Re: Re: RPATH status

Andrew Bartlett wrote:

>Not in particular, but an interesting point was made on
the fedora-devel
>list:  If the 'wrapped' binary forks a child, then that
unrelated child
>also inherits the environment, which may not be desired.

>  
>
FDS never forks anything. I suppose a perl backend or the
link
might _exec_ a child but I can't imagine why it would be
useful to fork 
ever.

>In Samba4, we 'solved' the similar problems (on a
smaller scale) by
>including the code statically.  I can't claim that's a
Superior
>solution...
>  
>
Bah ! I spent an entire weekend in 1996 making that code
into a shared 
library.


--
Fedora-directory-devel mailing list
Fedora-directory-develredhat.com
https://www.redhat.com/mailman/listinfo/fedora-dir
ectory-devel

David Boreham wrote:
> Andrew Bartlett wrote:
>
>> Not in particular, but an interesting point was
made on the fedora-devel
>> list:  If the 'wrapped' binary forks a child, then
that unrelated child
>> also inherits the environment, which may not be
desired.  
>>
> FDS never forks anything. I suppose a perl backend or
the link
> might _exec_ a child but I can't imagine why it would
be useful to 
> fork ever.
>
>> In Samba4, we 'solved' the similar problems (on a
smaller scale) by
>> including the code statically.  I can't claim
that's a Superior
>> solution...
>>  
>>
> Bah ! I spent an entire weekend in 1996 making that
code into a shared 
> library.
Fedora _strongly discourages_ the use of static libraries. 
They made us 
convert svrcore into a shared library so that it could be
included into 
Fedora [Extras].
>
>
> -- 
> Fedora-directory-devel mailing list
> Fedora-directory-develredhat.com
> https://www.redhat.com/mailman/listinfo/fedora-dir
ectory-devel

--
Fedora-directory-devel mailing list
Fedora-directory-develredhat.com
https://www.redhat.com/mailman/listinfo/fedora-dir
ectory-devel