Displaying 3 results from an estimated 3 matches for "stoppels".
Did you mean:
stopped
2024 Jan 10
1
Sys.which() caching path to `which`
.../opt/spack/linux-ubuntu18.04-x86_64_v3/gcc-7.5.0/r-4.3.0-eqteloqhjzix6ta373ruzt5imvvbcesc
Unfortunately, Spack packages are expected to get relocated, changing
the path prefix and invalidating stored paths, including the path to
`which`: <https://github.com/spack/spack/issues/41953>.
Harmen Stoppels, who is not subscribed to R-devel but interested in
making R work in Spack, currently creates a symlink to `which`
<https://github.com/r-devel/r-svn/pull/151> as part of a patch to R.
What would be the minimally disruptive way to avoid this dependency or
at least make it easier to fix post-f...
2024 Jan 10
0
Sys.which() caching path to `which`
...will change after installation - technically, it breaks the contract with the application. We are trying to get packages to not hard-code or cache paths, but that typically only applies to the package library location, not to system tools.
Cheers,
Simon
> On Jan 11, 2024, at 10:36 AM, Harmen Stoppels <me at harmenstoppels.nl> wrote:
>
> For context: I don't think Nix and Guix have to relocate anything, cause I think they require absolute paths like /nix/store where all binaries go. Spack on the other hand can install packages w/o sudo to a location of choice, e.g. ~/spack/opt/s...
2024 Jan 12
1
Sys.which() caching path to `which`
On Thu, 11 Jan 2024 09:30:55 +1300
Simon Urbanek <simon.urbanek at R-project.org> wrote:
> That said, WHICH is a mess - it may make sense to switch to the
> command -v built-in which is part of POSIX (where available - which
> is almost everywhere today) which would not require an external tool
This is a bit tricky to implement. I've prepared the patch at the end
of this