Re [PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

On Wed, 22 Nov 2017, Ævar Arnfjörð Bjarmason wrote: > > The latter case concerns me here. If the "Config" module is loading local > > system paths, then the relative pathing between "$Config{installsitelib}" > > and "$Config{siteprefixexp}" may not be consistent between systems, so an > > archive

Re: Re [PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

On Tue, Nov 21 2017, Dan Jacques jotted: > Ævar Arnfjörð Bjarmason @ 2017-11-20 21:50 UTC suggested: > >> So LeonT over at #p5p helped me with this. He believes this'll work >> (unless MakeMaker INSTALL_BASE is set, but that should break the Git >> install anyway): > > I think that the problem

Re [PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

Ævar Arnfjörð Bjarmason @ 2017-11-20 21:50 UTC suggested: > So LeonT over at #p5p helped me with this. He believes this'll work > (unless MakeMaker INSTALL_BASE is set, but that should break the Git > install anyway): I think that the problem with this approach is that it uses the local "Config"

Re: Re(2): [PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

On Mon, Nov 20 2017, Dan Jacques jotted: > On Mon, 20 Nov 2017 22:00:10, Ævar Arnfjörð Bjarmason replied: > >> [...] > > Thanks for responding. I'll readily confess that PERL and the PERL > ecosystem are not areas I'm very familiar with, so I'm really grateful > for your feedback here. > >> You

Re(2): [PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

On Mon, 20 Nov 2017 22:00:10, Ævar Arnfjörð Bjarmason replied: > [...] Thanks for responding. I'll readily confess that PERL and the PERL ecosystem are not areas I'm very familiar with, so I'm really grateful for your feedback here. > You need to bust the perl/PM.stamp cache as a function of

Re: [PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

On Mon, Nov 20 2017, Ævar Arnfjörð Bjarmason jotted: > On Sun, Nov 19 2017, Dan Jacques jotted: > >> [...] > > Firstly the promise of this is very neat. I'm happy to offer any help I > can give. > >> Enable Git to resolve its own binary location using a variety of >> OS-specific and generic

Re: [PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

On Sun, Nov 19 2017, Dan Jacques jotted: > [...] Firstly the promise of this is very neat. I'm happy to offer any help I can give. > Enable Git to resolve its own binary location using a variety of > OS-specific and generic methods, including: > > - procfs via "/proc/self/exe" (Linux) > -

Re: [PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

Dan Jacques writes: > Enable Git to resolve its own binary location using a variety of > OS-specific and generic methods, including: > > - procfs via "/proc/self/exe" (Linux) > - _NSGetExecutablePath (Darwin) > - KERN_PROC_PATHNAME sysctl on BSDs. > - argv0, if absolute (all,

[PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

Enable Git to resolve its own binary location using a variety of OS-specific and generic methods, including: - procfs via "/proc/self/exe" (Linux) - _NSGetExecutablePath (Darwin) - KERN_PROC_PATHNAME sysctl on BSDs. - argv0, if absolute (all, including Windows). This is used to enable

Re: [PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

Dan Jacques writes: > Enable Git to resolve its own binary location using a variety of > OS-specific and generic methods, including: > > - procfs via "/proc/self/exe" (Linux) > - _NSGetExecutablePath (Darwin) > - argv0, if absolute (all, including Windows). > > This is used to

[PATCH 1/1] exec_cmd: RUNTIME_PREFIX on some POSIX systems

Enable Git to resolve its own binary location using a variety of OS-specific and generic methods, including: - procfs via "/proc/self/exe" (Linux) - _NSGetExecutablePath (Darwin) - argv0, if absolute (all, including Windows). This is used to enable RUNTIME_PREFIX support for non-Windows systems,