You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It’d be a useful feature of the package manager if it could accept a version number (as an optional argument) to InstallPackage. This would be useful, for example, when using the PackageManager in continuous integration.
The text was updated successfully, but these errors were encountered:
I support this request. Today I ran into the following problem:
A package is already installed but its version is too old.
Thus I want to call InstallPackage programmatically but in a non-interactive way.
In this case, the function returns without trying to install the known newer version.
(If a version number is supported as an optional argument to InstallPackage then its meaning should be as in LoadPackage: "Take this version or a higher one except if the string starts with =".)
... as discussed in issue gap-packages#60
(I did not add tests of the new functionality,
first we should discuss whether the proposed change does what we want.)
ThomasBreuer
added a commit
to ThomasBreuer/PackageManager
that referenced
this issue
May 4, 2021
... as discussed in issue gap-packages#60
(I did not add tests of the new functionality,
first we should discuss whether the proposed change does what we want.)
It’d be a useful feature of the package manager if it could accept a version number (as an optional argument) to InstallPackage. This would be useful, for example, when using the PackageManager in continuous integration.
The text was updated successfully, but these errors were encountered: