Re: Installing packages to a foreign system
- To: Phillip Susi <psusi@cfl.rr.com>
- Cc: Goswin von Brederlow <goswin-v-b@web.de>, debian-dpkg@lists.debian.org
- Subject: Re: Installing packages to a foreign system
- From: Goswin von Brederlow <goswin-v-b@web.de>
- Date: Mon, 05 Oct 2009 11:08:20 +0200
- Message-id: <[🔎] 87fx9ynr7f.fsf@frosties.localdomain>
- In-reply-to: <4AC26641.9040805@cfl.rr.com> (Phillip Susi's message of "Tue, 29 Sep 2009 15:55:45 -0400")
- References: <4AB3F39A.3030202@cfl.rr.com> <87vdjaxbwe.fsf@frosties.localdomain> <4ABBDEE3.9010809@cfl.rr.com> <87ocovs4zt.fsf@frosties.localdomain> <4AC26641.9040805@cfl.rr.com>
Phillip Susi <psusi@cfl.rr.com> writes:
> On 9/28/2009 7:06 AM, Goswin von Brederlow wrote:
>> Phillip Susi<psusi@cfl.rr.com> 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
Reply to: