Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager
- To: itd <itd@firemail.cc>, 877331@bugs.debian.org
- Subject: Bug#877331: sponsorship-requests: nix/1.1.15 (ITP 877019) -- Purely functional package manager
- From: Kai Harries <kai.harries@gmail.com>
- Date: Sun, 20 Jan 2019 13:54:07 +0100
- Message-id: <[🔎] 87o98b4hhs.fsf@x230.kaiha.invalid>
- Reply-to: Kai Harries <kai.harries@gmail.com>, 877331@bugs.debian.org
- In-reply-to: <1edc9e40-ed35-e198-a686-d2e95eb82051@firemail.cc>
- References: <150678793402.12432.16761805795839797034.reportbug@nix230.fritz.box> <20180225140718.GA1723@belkar.wrar.name> <87r2p890oi.fsf@x230.kaiha.invalid> <20180226174647.GG1723@belkar.wrar.name> <E1gcS5e-0001UZ-K0@eggs.gnu.org> <150678793402.12432.16761805795839797034.reportbug@nix230.fritz.box> <87zhsr468y.fsf@x230.kaiha.invalid> <150678793402.12432.16761805795839797034.reportbug@nix230.fritz.box> <E1gdJQ6-0003nV-OZ@eggs.gnu.org> <150678793402.12432.16761805795839797034.reportbug@nix230.fritz.box> <m3muoojh9g.fsf@debian.org> <[🔎] E1gkwO6-0004C8-3t@eggs.gnu.org> <150678793402.12432.16761805795839797034.reportbug@nix230.fritz.box> <[🔎] 877ef0s9ap.fsf@x230.kaiha.invalid> <1edc9e40-ed35-e198-a686-d2e95eb82051@firemail.cc> <150678793402.12432.16761805795839797034.reportbug@nix230.fritz.box>
Hi,
itd <itd@firemail.cc> writes:
> Hi,
>
> Kai Harries:
>> The depender will break if the dependency is not at the path where it
>> used to be at build-time (by default /nix/store/...). All software
>> deployed by nix contains the full path to its dependencies. And all
>> dependencies are available inside the nix-store. The idea is to rely on
>> nothing that is outside the nix-store.
>
> would `mount --bind /var/nix /nix` help? In other words, Debian package
> nix uses /var/nix. Additionally, the package ships a Debian.README which
> states that users need to either bind mount /var/nix to /nix or to
> disable binary downloads.
Yes, bind mounts should work. I had started a discussion on d-devel [1]
on the topic of the non-standard-toplevel-dir, and from there I got the
impression that a lintian override is the way to go.
>From the user experience view I would prefer not to resort to a
bind-mount, but I guess your proposal should work and is the next best
thing I can imagine.
Regards Kai
[1] https://lists.debian.org/debian-devel/2019/01/msg00010.html
Reply to: