I just added something similar to the skarnet.org configure scripts
(except for skalibs which doesn't export binaries): the option is named
--enable-absolute-paths.
Patrick, can you please test it and tell me if it does what you want?
I also scrapped all the /sbin stuff and sbindir. Now
On Sun, Sep 11, 2016 at 12:49:30PM +0200, Laurent Bercot wrote:
> On 10/09/2016 21:31, Patrick Mahoney wrote:
> >Thoughts?
>
> >- exit 1
> >+# exit 1
>
> What was your problem with that? The weird Darwin thing where they
> hardcode the OS release number in the compiler's triple, and configure
On 10/09/2016 21:31, Patrick Mahoney wrote:
Thoughts?
- exit 1
+# exit 1
What was your problem with that? The weird Darwin thing where they
hardcode the OS release number in the compiler's triple, and configure
reported a spurious mismatch?
I'm of two minds here. On the one hand, I
On Sat, Aug 06, 2016 at 11:31:15AM +0200, Laurent Bercot wrote:
> On 2016-08-06 05:34, Patrick Mahoney wrote:
> >I'll hopefully have time to work on this in the coming days. Not sure what
> >best
> >to call the option. --enable-nix seems too specific. The Guix packager may
> >not
> >realize it
On 2016-08-06 05:34, Patrick Mahoney wrote:
I'll hopefully have time to work on this in the coming days. Not sure what best
to call the option. --enable-nix seems too specific. The Guix packager may not
realize it yet, but Guix needs this option as well (it is based on Nix).
"Naming is hard"
On Wed, Aug 03, 2016 at 08:59:40AM +0200, Laurent Bercot wrote:
> On 2016-08-03 04:08, Patrick Mahoney wrote:
> >Yes, but not in the way slashpackage does. Now that I understand what
> >these constants are for, it's clear that EXECLINE_BINPREFIX and
> >EXECLINE_EXTBINPREFIX should be defined to
On 2016-08-03 04:08, Patrick Mahoney wrote:
Yes, but not in the way slashpackage does. Now that I understand what
these constants are for, it's clear that EXECLINE_BINPREFIX and
EXECLINE_EXTBINPREFIX should be defined to point to the same absolute
bin directory of a specific Nix package of
On , Laurent Bercot wrote:
On 2016-08-02 19:41, Patrick Mahoney wrote:
Yes, the absolute path will be stable. This could be set at
configure time and would never change.
Let me repeat/rephrase my question: will it also be true if the
package,
or a dependency of the package, gets updated?
On 2016-08-02 19:41, Patrick Mahoney wrote:
Yes, the absolute path will be stable. This could be set at configure
time and would never change.
Let me repeat/rephrase my question: will it also be true if the package,
or a dependency of the package, gets updated?
With slashpackage, say for the
On , Laurent Bercot wrote:
On 2016-08-02 05:46, Patrick Mahoney wrote:
The Nix package manager is similar to slashpackage in that a given
version of s6 lives within a single directory (e.g. commands can be
found in /nix/store/$hash-s6-$version/bin/s6-*), however it does
not follow the
On 2016-08-02 05:46, Patrick Mahoney wrote:
The Nix package manager is similar to slashpackage in that a given version of
s6 lives within a single directory (e.g. commands can be found in
/nix/store/$hash-s6-$version/bin/s6-*), however it does not follow the
Hi,
Reading through the configure scripts in s6, s6-rc, etc., there doesn't seem to
be a way to set the binprefix (results in a definition for S6_BINPREFIX for
example) except by enabling slashpackage.
The Nix package manager is similar to slashpackage in that a given version of
s6 lives within
12 matches
Mail list logo
