Re: slashpackage again

From: Jorge Almeida <jjalmeida_at_gmail.com>
Date: Sat, 17 May 2014 07:05:00 +0100

On Sat, May 17, 2014 at 4:23 AM, Laurent Bercot <ska-skaware_at_skarnet.org> wrote:


> Slashpackage is about:
> - easy package management (having all your package data under a single
> directory, easy versioning, etc.)
> - Fixed full pathname guarantees, both versioned and non-versioned.

Sure, but the specification (so to speak) seems to imply that
"/.../s6/...." should be as good as "/.../s6-1.1.3.1/...." as long as
"s6" is a symlink to s6-1.1.3.1

>
> For an initramfs, you need neither of those, and the framework, as light
> as it is, is still too heavy for your needs. The price to pay is the forest
> of symlinks.

Not really a forest:

$ ls -l package
lrwxrwxrwx 1 root root 1 May 16 22:57 admin -> .
lrwxrwxrwx 1 root root 14 May 16 22:57 command -> /early/command
lrwxrwxrwx 1 root root 1 May 16 22:58 execline -> .
lrwxrwxrwx 1 root root 1 May 16 22:57 prog -> .
lrwxrwxrwx 1 root root 1 May 16 22:59 s6 -> .
lrwxrwxrwx 1 root root 1 May 16 22:59 s6-linux-utils -> .
lrwxrwxrwx 1 root root 1 May 16 22:59 s6-portable-utils -> .

It works if the symlink s6 is substituted by s6-1.1.3.1 (etc):
lrwxrwxrwx 1 root root 1 May 16 23:28 s6-1.1.3.1 -> .

(/early/command is the dir containing the binaries that are needed in
the initramfs)

But it is one more thing to remember updating after package upgrade

Thanks

Jorge

>
> --
> Laurent
>
Received on Sat May 17 2014 - 06:05:00 UTC