On Thu, May 15, 2014 at 11:08 PM, Laurent Bercot
wrote:
>> For example, for the execline package: am I right to assume that
>> binaries must be accessible in /package/admin/execline/command/, and
>> that this is the only requisite in order to be compatible with
>> slashpackage, at least when stat
I suppose I must take a closer look at which assumptions are involved.
You tell s6-svscan that the absolute path to the s6-supervise *from the
same package* is /command/s6-supervise. This is not true if you install
more than one version of s6.
You make /package and /command inseparable, when /
On Thu, May 15, 2014 at 9:49 PM, Laurent Bercot wrote:
> On 15/05/2014 20:43, Jorge Almeida wrote:
>>
>
>
>> Anyway, I have both /command and /package in the hard-drive based
>> system, and only /command in the initramfs. So, unless I'm missing
>> something, setting conf-home seems the best soluti
On 15/05/2014 20:43, Jorge Almeida wrote:
If I understand correctly, it would be less efficient (I tend to use
execve() rather than execvp() etc in my own little programs; searching
through a path when we already know the location of the binaries is
not appealing to me).
Sure, but honestly, th
On Thu, May 15, 2014 at 8:00 PM, Laurent Bercot wrote:
> On 15/05/2014 08:36, Jorge Almeida wrote:
>
> Yes, I remember we talked about it. And my answer was that
> flag-slashpackage will assume hard-coded paths work, because that's
> an important point of slashpackage (if not the whole point). I
On 15/05/2014 08:36, Jorge Almeida wrote:
We talked about this some time ago. If a binary is statically linked,
I would expect it to work wherever I put it, since it doesn't matter
whether any relevant libraries are there. I know now that this is not
true, because the binary may use some hard-cod
On Wed, May 14, 2014 at 11:50 PM, Laurent Bercot
wrote:
>
> power. The original daemontools utilities were lacking that, and I
> simply hadn't noticed until I added myself to some group in
> /etc/group and what I wanted to do didn't work because the processes
> behind s6-setuidgid didn't pick it
Is -DEXECLINE_OLD_VARNAMES still possible when compiling execline?
If so, maybe it should be mentioned (I find the old names more
readable, and besides there are scripts that would need to be changed,
always a possible source of mayhem when the scripts perform critical
functions!)
It is stil
Laurent,
Is -DEXECLINE_OLD_VARNAMES still possible when compiling execline?
If so, maybe it should be mentioned (I find the old names more
readable, and besides there are scripts that would need to be changed,
always a possible source of mayhem when the scripts perform critical
functions!)
Maybe
Hello,
It is time for the great Spring cleaning !
All existing skarnet.org packages have a new release.
* The versioning system has changed. Now I'm using 4-number versioning,
and the pattern is expected to remain stable. The reason for the change is
explained at http://skarnet.org/software/
10 matches
Mail list logo
