forcemerge 985416 985634
quit
Hi,
Thorsten Glaser wrote:
> I imagine *many* other third-party addons do the same.
Do you have examples? How do they approach being portable between
installations that set different gitexecdir directories at build time?
The directories being installed to are
* Thorsten Glaser [210423 16:00]:
> Chris Hofstaedtler dixit:
>
> >installation path. I imagine going back is now hopeless, so either
> >git searches both paths, or all other packages are just rc-buggy.
>
> I wasn’t considering just packages; unpackaged (or third-party-
> packaged) extensions
Chris Hofstaedtler dixit:
>installation path. I imagine going back is now hopeless, so either
>git searches both paths, or all other packages are just rc-buggy.
I wasn’t considering just packages; unpackaged (or third-party-
packaged) extensions will also be affected. Both paths is a good
plan.
* Thorsten Glaser [210419 21:26]:
> Package: git
> I imagine *many* other third-party addons do the same. Please
> make git search the old location after the new one (preferred)
> or revert this change at least until past the bullseye release
> (not preferred, as libexec is actually correct).
Hi again,
>I imagine *many* other third-party addons do the same. Please
>make git search the old location after the new one (preferred)
>or revert this change at least until past the bullseye release
>(not preferred, as libexec is actually correct).
ping?
Dixi quod…
>I imagine *many* other third-party addons do the same. Please
>make git search the old location after the new one (preferred)
Uhm, ping?
Package: git
Version: 1:2.31.0-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
git (1:2.31.0-1) unstable; urgency=low
* install dashed commands to /usr/libexec instead of /usr/lib (thx
Chris Lamb for suggesting it through lintian).
While this is laudable, some commands now fail:
7 matches
Mail list logo
