Re: Execlineb scripts on systems with conflicting binaries

2016-05-27 Thread Lorenzo
On 05/27/2016 01:04 PM, Laurent Bercot wrote: On 27/05/2016 12:31, Remko Tronçon wrote: Some of the 'built-in' binaries of execline conflict with binaries that already exist on the system. As far as I'm aware of, it's only import. Are there other binaries that conflict with other packages?

Re: s6-log error

2016-05-27 Thread Laurent Bercot
On 27/05/2016 06:59, Eric Vidal wrote: Creating a fifo file than having a s6-log watching on it? This. Anonymous pipes won't work here because you'd need to control a common ancestor to the processes you want to pipe. But named pipes do not have that requirement. - Create a fifo somewhere

Re: Execlineb scripts on systems with conflicting binaries

2016-05-27 Thread Eric Vidal
I got scared, is what I thought :) -- Eric Vidal

Re: Execlineb scripts on systems with conflicting binaries

2016-05-27 Thread Laurent Bercot
On 27/05/2016 13:17, Remko Tronçon wrote: The wrapper sounds like the best solution in my case I explicitly did not list it as a solution, and I kindly ask you not to do that. You are effectively removing execline binaries from PATH, which amounts to execline not really being installed on

Re: Execlineb scripts on systems with conflicting binaries

2016-05-27 Thread Laurent Bercot
On 27/05/2016 13:25, Eric Vidal wrote: You put me doubt. If my environment PATH is declared as it : PATH=/usr/bin:/usr/local/bin, the first import program taken is /usr/bin/import, not? i'm wrong? If PATH=/usr/bin:/usr/local/bin then "import" will *always* refer to /usr/bin/import, and you

Re: Execlineb scripts on systems with conflicting binaries

2016-05-27 Thread Eric Vidal
You put me doubt. If my environment PATH is declared as it : PATH=/usr/bin:/usr/local/bin, the first import program taken is /usr/bin/import, not? i'm wrong? -- Eric Vidal

Re: Execlineb scripts on systems with conflicting binaries

2016-05-27 Thread Laurent Bercot
On 27/05/2016 12:53, Eric Vidal wrote: I have installed execline at /usr/local/bin and the rest of s6 sofware at /usr/bin. Works like a charm. It works as long as nothing expects ImageMagick's import to be accessible via PATH search. If a program makes that assumption, it will break. --

Re: Execlineb scripts on systems with conflicting binaries

2016-05-27 Thread Laurent Bercot
On 27/05/2016 12:31, Remko Tronçon wrote: Some of the 'built-in' binaries of execline conflict with binaries that already exist on the system. As far as I'm aware of, it's only import. Are there other binaries that conflict with other packages? For example, on a system with imagemagick

Execlineb scripts on systems with conflicting binaries

2016-05-27 Thread Remko Tronçon
Hi, Some of the 'built-in' binaries of execline conflict with binaries that already exist on the system. For example, on a system with imagemagick installed, its 'import' gets precedence over the 'import' from execline. I know this is expected behavior, and can call '/bin/import' in all my

Re: Skalibs & Execline build on OS X

2016-05-27 Thread Remko Tronçon
> I'm not interested in supporting dynamic libraries on MacOS X, for this > and other reasons. Please read the README.macosx file in the skalibs and > execline packages. > Oops, missed that, sorry. Thanks. I assume you don't like making this a default for 'configure' on Darwin systems? What