Releases: r-lib/pak
pak 0.5.1
- No user visible changes.
pak 0.5.0
-
The
meta_*()functions now consider theplatforms,cran_mirrorand
r_versionsconfig entries, see?"pak-config". -
Better Posit Package Manager (PPM) support. New
+ppm_has_binaries(),
ppm_r_versions(),ppm_repo_url(),ppm_snapshots()andppm_platforms()
functions to help interacting with PPM. See the new 'pkgcache and Posit
Package Manager on Linux' article at https://r-lib.github.io/pkgcache.
(r-lib/pkgcache#47 and r-lib/pkgdepends#186). -
New
system_r_platform()andsystem_r_platform_data()functions to query
the current platform. -
pak now support git repositories as package references. E.g.
git::https://github.com/r-lib/pak.git. -
pak now supports versioned CRAN packages, e.g.
[email protected]will
always install dplyr 1.1.1. Note that only CRAN packages are supported,
Bioconductor packages are not (yet). -
pak now has an alternative system requirements lookup
implementation. It supports Fedora and Debian systems as well, in
addition to Debian, Ubuntu, SUSE and RedHat derivatives.
You can switch to this implementation by setting the
R_PKG_SYSREQS2environment variable totrue. -
pak now does a better job looking up dependencies for
hand-selected dependency types. E.g.dependencies = "LinkingTo". -
pak now removes
?ignore-d packages from dependencies, and
uses the correct version comparison for?ignore-before.r
(r-lib/actions#708). -
pak now does not fail for circular soft dependencies (#306).
-
pak now reports dependency solver failures better in some cases
(#305, #474). -
pak now uses locally built CRAN binaries from the cache. Use the
?nocacheparameter to opt out from this, or
cache_delete(package = ...)to remove a package from the cache.
pak 0.4.0
-
pak has much improved and more informative error messages now.
This work is not yet finished, so if you find an unclear error message,
please open an issue. Thank you! -
The solver is now more robust for non-canonical input (e.g.
DESCRIPTION
files) (#423). -
Better installation output. Standard output and error are now
collected together (r-lib/pkgdepends@0669f0f8c). -
The solver is now doing a better job when multiple versions of the
same package are present in the same repository
(r-lib/actions#559). -
pkg_name_check()now works again, it needed a fix after changes at
https://crandb.r-pkg.org. -
Explicit package names in local and URL package sources, as in
package=local::...orpackage=url::...are now parsed correctly in
dependencies. -
pak is now more robust to
Archsfields missing from the CRAN
metadata for packages with compiled code
(#448). -
url::packages now always work correctly, even if the digest package is
not installed (#433). -
pak is now more robust when installing packages from subdirectories
of GitHub repositories (#431,
@paleolimbot). -
Parameters
?reinstall,?sourceand?ignorenow work correctly when
specified in thepackage=?parameterformat (#294). -
The
?ignoreparameter works correctly now. -
Dependency resolution now does not fail if a package is not found.
-
pak can now install
url::remotes from GitHub. -
pak now does not fail when the package of a
.tar.gzGitHub
snapshot is in a subdirectory, or in a subdirectory of a subdirectory. -
pak now errors early if it cannot deduce the name of the package
from aRemotesorConfig/Needs/*entry. -
Solver failures now include details in some cases where previously they
did not. -
pak can now update packages in Docker containers where the
old version was installed in the different Docker later
(#251) -
Update R version -> Bioconductor version mapping. R 4.2.x now maps to
Bioconductor 3.16.
pak 0.3.1
-
The
?ignoreparameter works correctly now. -
Dependency resolution now does not fail if a package is not found.
-
pak can now install
url::remotes from GitHub. -
pak now does not fail when the package of a
.tar.gzGitHub
snapshot is in a subdirectory, or in a subdirectory of a subdirectory. -
pak now errors early if it cannot deduce the name of the package
from aRemotesorConfig/Needs/*entry. -
Solver failures now include details in some cases where previously they
did not. -
pak can now update packages in Docker containers where the
old version was installed in the different Docker later (#251) -
pak errors are now user friendlier and better formatted.
-
pak now does not load tibble and its dependencies in the pak subprocess,
so their dlls are not locked by the pak subprocess on Windows. -
pak now does not fail when installing a package that uses a non-UTF-8
encoding on R 4.3.x and later (#404).
pak 0.3.0
-
pak functions that used to return tibbles return data frames now.
While data frames and tibbles are very similar, they are not completely
compatible. To convert the outputs of pak functions to tibbles call the
tibble::as_tibble()function on them. If the pillar package is loaded,
it improves the printing of the returned data frames.Relatedly,
pak::pak_install_extra()installs pillar now, instead of tibble. -
pak now supports
file://repositories. -
pak now uses HTTP 1.1 to download packages on Linux, in addition to macOS.
This fixes HTTP issues with some servers (#358). -
New
?ignore-before-rparameter to ignore optional dependencies that
need a newer R version (r-lib/pkgdepends#243). -
New
?ignoreparameter to ignore an optional dependency. -
Allow specifying downstream package parameters with the
package=?param
syntax. -
lockfile_install()now works better forany::refs, and pak always
install the version it has planned for. -
System requirement installation is now more robust and works for
Unix shell expressions (#347). -
CRAN-like resolution is more robust now if a repository is missing
the usual metadata. -
The lock file is pretty JSON now.
-
pak now handles all version requirement types properly:
'<', '<=',==,>=,>. -
The dependency solver now uses better heuristics and does not
(effectively) freeze if multiple repositories have multiple versions of
the same packages (e.g. RSPM and CRAN)
(r-lib/pkgdepends#277)
v0.2.1
No user visible changes.
v0.2.0
Lots of news, too much to list. This is a completely new package now.
v0.1.2
First release on CRAN.