Welcome to the 44th post in the $R^4 series.
A few weeks ago, and following an informal call for talks by James Lamb, I had an opportunity
to talk about r2u to
the Chicago ML and MLops meetup groups. You can find
the slides
here.
Over the last 2 1/2 years, r2u has become a
widely-deployed mechanism in a number of settings, including (but not
limited to) software testing via continuous integration, deployment on
cloud servers besides of course to more standard use on local laptops or
workstation. 30
million downloads illustrate this. My thesis for the talk was that
this extends equally to ML(ops) where no surprises, no hickups
automated deployments are key for large-scale model training, evaluation
and of course production deployments.
In this context, I introduce r2u while giving credit
both to what came before it, the existing alternatives (or competitors
for mindshare if one prefers that phrasing), and of course what lies
underneath it.
The central takeaway, I argue, is that r2u can and does take
advantage of a unique situation in that we can join the package
manager task for the underlying (operating) system and and the
application domain, here R and
its unique CRAN repository
network. Other approaches can, and of course do, provide binaries, but
by doing this outside the realm of the system package manager
can only arrive at a lesser integration (and I show a common error
arising in that case). So where r2u is feasible, it
dominates the alternatives (while the alternatives may well provide
deployment on more platforms which, even when less integrated, may be of
greater importance for some). As always, it all depends.
But the talk, and its slides,
motivate and illustrate why we keep calling r2u by its slogan of
r2u: Fast. Easy. Reliable. Pick All Three.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. If you like this or other open-source work I do, you can now sponsor me at GitHub. Please report excessive re-aggregation in third-party for-profit settings.
A new release 0.2.13 of RcppCCTZ is
now on CRAN.
RcppCCTZ
uses Rcpp to bring CCTZ to R. CCTZ is a C++ library for
translating between absolute and civil times using the rules of a time
zone. In fact, it is two libraries. One for dealing with
civil time: human-readable dates and times, and one for
converting between between absolute and civil times via time zones. And
while CCTZ is made by
Google(rs), it is not an official Google product. The RcppCCTZ
page has a few usage examples and details. This package was the first CRAN package to use CCTZ; by now several others
packages (four the last time we counted) include its sources too. Not
ideal, but beyond our control.
This version include most routine package maintenance as well as one
small contributed code improvement. The changes since the last CRAN release are summarised
below.
Courtesy of my CRANberries, there is a diffstat report relative to to the previous version. More details are at the RcppCCTZ page; code, issue tickets etc at the GitHub repository. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in version 0.2.13 (2024-12-11)
- No longer set compilation standard as recent R version set a sufficiently high minimum
- Qualify a call to
cctz::format(Michael Quinn in #44)- Routine updates to continuous integration and badges
- Switch to Authors@R in DESCRIPTION
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A new version of our pinp package
arrived on CRAN today, and is
the first release in four years. The pinp package
allows for snazzier one or two column Markdown-based pdf vignettes, and
is now used by a few packages. A screenshot of the package vignette can
be seen below. Additional screenshots are at the pinp page.
This release contains no new features or new user-facing changes but
reflects the standard package and repository maintenance over the
four-year window since the last release: updating of actions, updating
of URLs and addressing small packaging changes spotted by
ever-more-vigilant R checking code.
The NEWS entry for this release follows.
Courtesy of my CRANberries, there is a diffstat report relative to previous release. More detailed information is on the ping page. For questions or comments use the issue tracker off the GitHub repo. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in pinp version 0.0.11 (2024-12-08)
- Standard package maintenance for continuous integration, URL updates, and packaging conventions
- Correct two minor nags in the Rd file
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
Armadillo is a powerful
and expressive C++ template library for linear algebra and scientific
computing. It aims towards a good balance between speed and ease of use,
has a syntax deliberately close to Matlab, and is useful for algorithm
development directly in C++, or quick conversion of research code into
production environments. RcppArmadillo
integrates this library with the R environment and language and is
widely used by (currently) 1197 other packages on CRAN, downloaded 37.5 million
times (per the partial logs from the cloud mirrors of CRAN), and the CSDA paper (preprint
/ vignette) by Conrad and myself has been cited 605 times according
to Google Scholar.
Conrad released a minor
version 14.2.2 yesterday. This followed a bit of recent work a few of us
did in the ensmallen
and mlpack repositories
following the [14.2.0 release]. Use of (member functions)
.min(index) and .max(index) was deprecated in
Armadillo in favor of
.index_mix() and .index_max(). By now ensmallen and mlpack have been
updated at CRAN. To add some
spice, CRAN emailed that the
(very much unreleased as of now, but coming likely next spring) gcc-15
was unhappy with RcppArmadillo
due to some Armadillo code.
This likely related to the listed gcc-15 C++
change about Qualified name lookup failure into the current
instantiation . Anyway, Conrad fixed it within days
and that change too is part of this new version (as is a small behaviour
normalization between the two indexing methods that matters in case of
ties, this was in 14.2.1).
The changes since the last CRAN release are summarised
below.
Courtesy of my CRANberries, there is a diffstat report relative to previous release. More detailed information is on the RcppArmadillo page. Questions, comments etc should go to the rcpp-devel mailing list off the Rcpp R-Forge page. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in RcppArmadillo version 14.2.2-1 (2024-12-05)
- Upgraded to Armadillo release 14.2.2 (Smooth Caffeine)
- Workarounds for regressions in pre-release versions of GCC 15
- More selective detection of symmetric/hermitian matrices by various functions
Changes in RcppArmadillo version 14.2.1-1 (2024-11-24) (GitHub Only)
- Upgraded to Armadillo release 14.2.1 (Smooth Caffeine)
- Fix for
index_min()andindex_max()to ensure that the first index of equal extremum values is found
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
An updated version of the corels package is
now on CRAN! The Certifiably
Optimal RulE ListS (Corels) learner provides interpretable decision
rules with an optimality guarantee a nice feature which sets it apart in
machine learning. You can learn more about corels at its UBC site.
The changes concern mostly maintenance for both the repository (such
as continunous integration setup, badges, documentation links, ) and
the package level (such as removing the no-longer-requiring C++
compilation standard setter now emitting a NOTE at CRAN.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A new release of the anytime
package arrived on CRAN
today the first is well over four years. The package is fairly
feature-complete, and code and functionality remain mature and stable,
of course.
anytime
is a very focused package aiming to do just one thing really
well: to convert anything in integer, numeric, character,
factor, ordered, input format to either POSIXct (when called as
anytime) or Date objects (when called as
anydate) and to do so without requiring a format
string as well as accomodating different formats in one input
vector. See the anytime page,
or the GitHub repo
for a few examples, and the beautiful documentation site
for all documentation.
This release slowly matured over four years. It combines a number of
strictly internal repository maintenance such as changes to continuous
integration with small enhancements (adding for example some new
formats, responding better to an error condition, dealing with logical
input as an error) with a relaxation of the C++ compilation standard.
While we once needed C++11, it is now a constraint as as R itself is quite proactive (the
last two releases defaulted already to C++17, suitable compiler
permitting) we can now relax this constraint. The documentation site is
new, as some other small changes. See the full list of changes which
follows.
Courtesy of my CRANberries, there is also a diffstat report of changes relative to the previous release. The issue tracker tracker off the GitHub repo can be use for questions and comments. More information about the package is at the package page, the GitHub repo and the documentation site. If you like this or other open-source work I do, you can now sponsor me at GitHub.Changes in anytime version 0.3.10 (2024-12-02)
- A new documentation site was added.
- Continuous Integration now uses
run.shfrom r-ci with bspm- Logical input vectors are now recognised as an error (#121)
- Additional dot-separated format
'%Y.%m.%d'is supported- Other small updates were made throughout the package
- No longer set a C++ compilation standard as the default choices by R are sufficient for the package
- Switch Rcpp include file to Rcpp/Lightest
- We recommend
~/.R/Makevarscompiler flag options-Wno-ignored-attributes -Wno-nonnull -Wno-parentheses- The tinytest runner was simplified
NAvalues from conversion now trigger a warning
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A new version of the RcppAPT
package arrived on CRAN earlier
today. RcppAPT
connects R to the C++ library behind the awesome apt,
apt-get, apt-cache, commands (and their
cache) which powering Debian, Ubuntu and other derivative
distributions.
RcppAPT
allows you to query the (Debian or Ubuntu) package dependency graph at
will, with build-dependencies (if you have deb-src
entries), reverse dependencies, and all other goodies. See the vignette
and examples for illustrations.
This release moves the C++ compilation standard from C++11 to C++17.
I had removed the setting for C++11 last year as compilation by
compiler default worked well enough. But the version at CRAN still carried, which started
to lead to build failures on Debian unstable so it was time for an
update. And rather than implicitly relying on C++17 as selected
by the last two R releases, we made it explicit. Otherwise a few of the
regular package and repository updates have been made, but no new code
or features were added The NEWS entries follow.
Courtesy of my CRANberries, there is also a diffstat report for this release. A bit more information about the package is available here as well as at the GitHub repo. If you like this or other open-source work I do, you can now sponsor me at GitHub.Changes in version 0.0.10 (2024-11-29)
- Package maintenance updating continuous integration script versions as well as coverage link from README, and switching to Authors@R
- C++ compilation standards updated to C++17 to comply with libapt-pkg
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
Speakers: Melissa Wen (Igalia) and Rodrigo Siqueira (AMD)
Link: https://indico.freedesktop.org/event/6/contributions/383/
Topics: Similar to the hackfest, the meeting agenda was built over the
first two days of the conference and mixed talks follow-up with new ideas and
ongoing community efforts.
The final agenda covered five topics in the scheduled order:
From his notes, let s dive into the key discussions!
Armadillo is a powerful
and expressive C++ template library for linear algebra and scientific
computing. It aims towards a good balance between speed and ease of use,
has a syntax deliberately close to Matlab, and is useful for algorithm
development directly in C++, or quick conversion of research code into
production environments. RcppArmadillo
integrates this library with the R environment and language and is
widely used by (currently) 1191 other packages on CRAN, downloaded 37.2 million
times (per the partial logs from the cloud mirrors of CRAN), and the CSDA paper (preprint
/ vignette) by Conrad and myself has been cited 603 times according
to Google Scholar.
Conrad released a minor
version 14.2.0 a few days ago after we spent about two weeks with
several runs of reverse-dependency checks covering corner cases. After a
short delay at CRAN due to a
false positive on a test, a package failing tests we also failed under
the previous version, and some concern over new deprecation warnings
_whem using the headers directly as _e.g. mlpack R package
does we are now on CRAN. I
noticed a missing feature under large 64bit word (for large
floating-point matrices) and added an exporter for icube
going to double to support the 64-bit integer range (as we
already did, of course, for vectors and matrices). Changes since the
last CRAN release are
summarised below.
Courtesy of my CRANberries, there is a diffstat report relative to previous release. More detailed information is on the RcppArmadillo page. Questions, comments etc should go to the rcpp-devel mailing list off the Rcpp R-Forge page. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in RcppArmadillo version 14.2.0-1 (2024-11-16)
- Upgraded to Armadillo release 14.2.0 (Smooth Caffeine)
- Faster handling of symmetric matrices by
inv()andrcond()- Faster handling of hermitian matrices by
inv(),rcond(),cond(),pinv(),rank()- Added
solve_opts::force_symoption tosolve()to force the use of the symmetric solver- More efficient handling of compound expressions by
solve()- Added exporter specialisation for
icubefor theARMA_64BIT_WORDcase
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
| Series: | Bright Falls #1 |
| Publisher: | Jove |
| Copyright: | February 2022 |
| ISBN: | 0-593-33641-0 |
| Format: | Kindle |
| Pages: | 374 |
Version 0.0.19 of RcppSpdlog arrived
on CRAN early this morning and
has been uploaded to Debian. RcppSpdlog
bundles spdlog, a
wonderful header-only C++ logging library with all the bells and
whistles you would want that was written by Gabi Melman, and also includes fmt by Victor Zverovich. You can learn
more at the nice package
documention site.
This releases updates the code to the version 1.15.0 of spdlog which was released on
Saturday, and contains fmt
11.0.2. It also contains a contributed PR which allows use
std::format under C++20, bypassing fmt (with
some post-merge polish too), and another PR correcting a documentation
double-entry.
The NEWS entry for this release follows.
Courtesy of my CRANberries, there is also a diffstat report. More detailed information is on the RcppSpdlog page, or the package documention site. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in RcppSpdlog version 0.0.19 (2024-11-10)
- Support use of
std::formatunder C++20 via opt-in define instead offmt(Xanthos Xanthopoulos in #19)- An erroneous duplicate log=level documentation level was removed (Contantinos Giachalis in #20)
- Upgraded to upstream release spdlog 1.15.0 (Dirk in #21)
- Partially revert / simplify
src/formatter.cppaccomodating both #19 and previous state (Dirk in #21)
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A new release of the inline package got
to CRAN today marking the first
release in three and half years. inline facilitates
writing code in-line in simple string expressions or short
files. The package was used quite extensively by Rcpp in the very early days before Rcpp
Attributes arrived on the scene providing an even better alternative
for its use cases. inline is still
used by rstan and
a number of other packages.
This release was tickled by changing in r-devel just this week, and
the corresponding please fix or else email I received this morning.
R_NO_REMAP is now the default in r-devel, and while we had
already converted most (old-style) calls into the API to using the now
mandatory Rf_ prefix, the package contained few remaining
cases in examples as well as one in code generation. The release also
contains a helpful contributed PR making an error message a little
clearer, plus several small and common maintenance changed around
continuous integration, package layout and the repository.
The NEWS extract follows and details the changes some
more.
Thanks to my CRANberries, you can also look at a diff to the previous release Questions, comments etc should go to the rcpp-devel mailing list off the R-Forge page. Bugs reports are welcome at the GitHub issue tracker as well (where one can also search among open or closed issues). If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in inline version 0.3.20 (2024-11-10)
- Error message formatting is improved for
compileCode(Alexis Derumigny in #25)- Switch to using Authors@R, other general packaging maintenance for continuous integration and repository
- Use
Rf_in a handful of cases as R-devel now mandates it
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
Welcome to the October 2024 report from the Reproducible Builds project.
Our reports attempt to outline what we ve been up to over the past month, highlighting news items from elsewhere in tech where they are related. As ever, if you are interested in contributing to the project, please visit our Contribute page on our website.
Table of contents:
Jens Dietrich, Tim White, of Victoria University of Wellington, New Zealand along with Behnaz Hassanshahi and Paddy Krishnan of Oracle Labs Australia published a paper entitled Levels of Binary Equivalence for the Comparison of Binaries from Alternative Builds :
The availability of multiple binaries built from the same sources creates new challenges and opportunities, and raises questions such as: Does build A confirm the integrity of build B? or Can build A reveal a compromised build B? . To answer such questions requires a notion of equivalence between binaries. We demonstrate that the obvious approach based on bitwise equality has significant shortcomings in practice, and that there is value in opting for alternative notions. We conceptualise this by introducing levels of equivalence, inspired by clone detection types.A PDF of the paper is freely available.
On Friday 8th November, Vagrant Cascadian will present a talk entitled Two Ways to Trustworthy at SeaGL in Seattle, WA.
Founded in 2013, SeaGL is a free, grassroots technical summit dedicated to spreading awareness and knowledge about free source software, hardware and culture. Vagrant s talk:
[ ] delves into how two project[s] approaches fundamental security features through Reproducible Builds, Bootstrappable Builds, code auditability, etc. to improve trustworthiness, allowing independent verification; trustworthy projects require little to no trust. Exploring the challenges that each project faces due to very different technical architectures, but also contextually relevant social structure, adoption patterns, and organizational history should provide a good backdrop to understand how different approaches to security might evolve, with real-world merits and downsides.
the D8 Java to DEX compiler (part of the Android toolchain) eliminated a redundant field load if running the class s static initialiser was known to be free of side effects, which ended up accidentally depending on the sharding of the input, which is dependent on the number of CPU cores used during the build.To make it easier to understand the bug and the patch, Fay also made a small example to illustrate when and why the optimisation involved is valid.
CONFIG_MODULE_SIG and the unreproducible Linux Kernel to add: I wonder whether it would be possible to use the Linux kernel s Integrity Policy Enforcement to deploy a policy that would prevent loading of anything except a set of expected kernel modules. [ ]
diffoscope is our in-depth and content-aware diff utility that can locate and diagnose reproducibility issues. This month, Chris Lamb made the following changes, including preparing and uploading versions 279, 280, 281 and 282 to Debian:
.ar archives (#1085257). [ ]systemd-ukify in the Debian stable distribution. [ ]Depends on the deprecated python3-pkg-resources (#1083362). [ ]
The IzzyOnDroid project has reached a good milestone by reaching over 25% of the ~1,200 Android apps provided by their repository (of official APKs built by the original application developers) having been confirmed to be reproducible by a rebuilder.
In Debian this month:
devscripts version 2.24.2, including many changes to the debootsnap, debrebuild and reproducible-check scripts. This is the first time that debrebuild actually works (using sbuild s unshare backend). As part of this, Holger also fixed an issue in the reproducible-check script where a typo in the code led to incorrect results [ ]
The new server has no problems keeping up with importing the full archives on every update, as each run finishes comfortably in time before it s time to run again. [While] the new server is the one doing all the importing of updated archives, the HTTP interface is being served by both the new server and one of the VM s at LeaseWeb.The entry list a number of specific updates surrounding the API endpoints and rate limiting.
Elsewhere in distribution news, Zbigniew J drzejewski-Szmek performed another rebuild of Fedora 42 packages, with the headline result being that 91% of the packages are reproducible. Zbigniew also reported a reproducibility problem with QImage.
Finally, in openSUSE, Bernhard M. Wiedemann published another report for that distribution.
There were an enormous number of improvements made to our website this month, including:
hulkoba
README page for building the website under NixOS. [ ][ ][ ][ ][ ]
The Reproducible Builds project operates a comprehensive testing framework running primarily at tests.reproducible-builds.org in order to check packages and other artifacts for reproducibility. In October, a number of changes were made by Holger Levsen, including:
index.html for rebuilderd. [ ]nginx.conf configuration file for rebuilderd. [ ]riscv64 architecture. [ ]rebuilderd-related TODO. [ ]inos5 node [ ] and Vagrant Cascadian brought 4 virt nodes back online [ ].
The Open Source Summit EU took place recently, and covered plenty of topics related to supply-chain security, including:
apache-ivy (.zip modification time)ccache (build failure)colord (CPU)efivar (CPU/march=native)gsl (no check)libcamera (date/copyright year)libreoffice (possible rpm/build toolchain corruption bug)moto (.gz modification time)openssl-1_1 (date-related issue)python-pygraphviz (benchmark)sphinx/python-pygraphviz (benchmark)python-panel (package.lock has random port)python-propcache (random temporary path)python314 (.gz-related modification time)rusty_v8 (random .o files)scapy (date)wine (parallelism)ibmtss (FTBFS-2026)pymol (date)pandas (ASLR)linutil (drop date)lsof (also filed in openSUSE: uname -r in LSOF_VSTR)schily (also filed in openSUSE: uname -r)superlu (nocheck)util (random test failure)ceph (year-2038 variation from embedded boost)distro-info.calibre (two sort issues) [ ][ ]#reproducible-builds on irc.oftc.net.
rb-general@lists.reproducible-builds.org
A hot-fix release 1.0.13-1, consisting of two small PRs relative to
the last regular CRAN release
1.0.13,
just arrived on CRAN. When we
prepared 1.0.13,
we included a change related to the tightening of the C API of R
itself. Sadly, we pinned an expected change to comes with next (minor)
release 4.4.2 rather than now next (normal aka major) release 4.5.0 .
And now that R 4.4.2 is out (as of two days ago) we accidentally broke
building against the header file with that check. Whoops. Bugs happen,
and we are truly sorry but this is now addressed in 1.0.13-1.
The normal (bi-annual) release cycle will resume with 1.0.14 slated
for January. As you can see from the NEWS
file of the development branch, we have a number of changes coming.
You can safely access that release candidate version, either off the
default branch at github or via r-universe artifacts.
The list below details all changes, as usual. The only other change
concerns the now-mandatory use of Authors@R.
Thanks to my CRANberries, you can also look at a diff to the previous release Questions, comments etc should go to the rcpp-devel mailing list off the R-Forge page. Bugs reports are welcome at the GitHub issue tracker as well (where one can also search among open or closed issues). If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in Rcpp release version 1.0.13-1 (2024-11-01)
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
# https://www.reddit.com/r/thinkpad/comments/1blpy20/comment/kw7se2l/?context=3 [Unit] Description=Workarounds for sleep wakeup source for Thinkpad X1 Yoga 3 After=sysinit.target After=systemd-modules-load.service [Service] Type=oneshot ExecStart=/bin/sh -c "echo 'enabled' > /sys/devices/platform/i8042/serio0/power/wakeup" ExecStart=/bin/sh -c "echo 'enabled' > /sys/devices/platform/i8042/serio1/power/wakeup" ExecStart=/bin/sh -c "echo 'LID' > /proc/acpi/wakeup" [Install] WantedBy=multi-user.targetNow it works fine, for stylus at least. I still get kernel error messages like the following which don t seem to cause problems:
wacom 0003:056A:5146.0005: wacom_idleprox_timeout: tool appears to be hung in-prox. forcing it out.When it wasn t working I got the above but also kernel error messages like:
wacom 0003:056A:5146.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop eventsThis change affected the way suspend etc operate. Now when I connect the laptop to power it will leave suspend mode. I ve configured KDE to suspend when the lid is closed and there s no monitor connected.
Another pure maintenance release 0.2.7 of the gcbd package is now on
CRAN. The gcbd proposes a
benchmarking framework for LAPACK and BLAS operations (as the library
can exchanged in a plug-and-play sense on suitable OSs) and records
result in local database. Its original motivation was to also compare to
GPU-based operations. However, as it is both challenging to keep CUDA
working packages on CRAN
providing the basic functionality appear to come and go so testing the
GPU feature can be challenging. The main point of gcbd is now to actually
demonstrate that yes indeed we can just swap BLAS/LAPACK libraries
without any change to R, or R packages. The configure / rebuild R for
xyz often seen with xyz being Goto or MKL is simply plain wrong: you
really can just swap them (on proper operating systems, and R
configs see the package vignette for more). But nomatter how often we
aim to correct this record, it invariably raises its head another
time.
This release accommodates a CRAN change request as we were
referencing the (now only suggested) package gputools. As
hinted in the previous paragraph, it was once on CRAN but is not right now so we
adjusted our reference.
CRANberries
also provides a diffstat report for
the latest release.
If you like this or other open-source work I do, you can sponsor me at
GitHub.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
A new minor release of the drat package
arrived on CRAN today, which is
just over a year since the previous release. drat stands for
drat R Archive Template, and helps with easy-to-create and
easy-to-use repositories for R packages. Since its inception in
early 2015 it has found reasonably widespread adoption among R users
because repositories with marked releases is the better way to
distribute code.
Because for once it really is as your mother told you: Friends
don t let friends install random git commit snapshots. Properly
rolled-up releases it is. Just how CRAN shows us: a model that has
demonstrated for over two-and-a-half decades how to do this.
And you can too: drat is easy to use, documented by six
vignettes and just works. Detailed information about
drat is at its documentation site. That
said, and these days , if you mainly care about github code then r-universe is there too, also
offering binaries its makes and all that jazz. But sometimes you just
want to, or need to, roll a local repository and drat can help
you there.
This release contains a small PR (made by Arne Holmin just after the
previous release) adding support for an OSflacour variable (helpful
for macOS). We also corrected an issue with one test file being
insufficiently careful of using git2r only when installed,
and as usual did a round of maintenance for the package concerning both
continuous integration and documentation.
The NEWS file summarises the release as follows:
Courtesy of my CRANberries, there is a comparison to the previous release. More detailed information is on the drat page as well as at the documentation site. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in drat version 0.2.5 (2024-10-21)
- Function
insertPackagehas a new optional argumentOSflavour(Arne Holmin in #142)- A test file conditions correctly about git2r being present (Dirk)
- Several smaller packaging updates and enhancements to continuous integration and documentation have been added (Dirk)
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
The thirteenth release of the qlcal package
arrivied at CRAN today.
qlcal
delivers the calendaring parts of QuantLib. It is provided (for the R
package) as a set of included files, so the package is self-contained
and does not depend on an external QuantLib library (which can be
demanding to build). qlcal covers
over sixty country / market calendars and can compute holiday lists, its
complement (i.e. business day lists) and much more. Examples
are in the README at the repository, the package page,
and course at the CRAN package
page.
This releases synchronizes qlcal with
the QuantLib release 1.36 (made
this week) and contains some minor updates to two calendars.
Courtesy of my CRANberries, there is a diffstat report for this release. See the project page and package documentation for more details, and more examples. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in version 0.0.13 (2024-10-15)
- Synchronized with QuantLib 1.36 released yesterday
- Calendar updates for South Korea and Poland
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
RcppDate wraps
the featureful date
library written by Howard
Hinnant for use with R. This header-only modern C++ library has been
in pretty wide-spread use for a while now, and adds to C++11/C++14/C++17
what will be (with minor modifications) the date library in C++20.
This release, the first in 3 1/2 years, syncs the code with the
recent date 3.0.2
release from a few days ago. It also updates a few packaging details
such as URLs, badges or continuous integration.
Courtesy of my CRANberries, there is also a diffstat report for the most recent release. More information is available at the repository or the package page. If you like this or other open-source work I do, you can sponsor me at GitHub.Changes in version 0.0.4 (2024-10-14)
- Updated to upstream version 3.0.2 (and adjusting one pragma)
- Several small updates to overall packaging and testing
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.
Next.