Phillip Susi <[email protected]> writes:
> On 9/28/2009 7:06 AM, Goswin von Brederlow wrote:
>> Phillip Susi<[email protected]> writes:
>>
>>> This looks like it does the trick, but I am curious; is this how the
>>> installer does it? When the installer is first installing the system
>>> it also needs to install the packages to the hard disk, but without
>>> having them interfere with the running state of the installing system.
>>> Is this how it does that?
>> It is what policy dictates for every package. Would be stupid to
>> invent something else.
>
> So is a package broken if its configure script invokes tools that rely
> on a running daemon, and the configure fails if the tools can't
> contact the daemon? Like say, udevinfo?
Verry problematic.
It gets even worse. What if it contacts the daemon runing outside the
chroot and gets totaly the wrong information?
MfG
Goswin
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
