This is the mail archive of the
mailing list for the Cygwin project.
Re: Default script installation
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-apps at cygwin dot com
- Date: Sun, 2 Mar 2003 13:00:56 -0500
- Subject: Re: Default script installation
- References: <NCEBJJFMCAOKNNABBFIMOEPFDBAA.email@example.com> <002d01c2e0e4$08260570$78d96f83@pomello>
- Reply-to: cygwin-apps at cygwin dot com
On Sun, Mar 02, 2003 at 05:49:10PM -0000, Max Bowsher wrote:
>Forwarding to the list:
>John Morrison wrote:
>>> From: Max Bowsher
>>> John Morrison wrote:
>>>> Was anything ever decided about this? Pierre wants
>>>> me to update the /etc/profile package which would
>>>> be an ideal first candidate for this.
>>> You can't guarantee that autodep packages will be installed at the
>>> right time.
>>> How about including a copy of the update-defaults postinstall script
>>> in every package that installs files to /etc/defaults ?
>> I didn't want to force folks to do anything :(
>And now replying:
>The autodep method just about works for Base packages, but is simply not an
>option for any non-Base packages. So if any non-Base packages are to use
>/etc/defaults/, it's really not feasible at all.
Why does it have anything to do with Base packages? We know it isn't
a perfect solution. We've discussed this to death.
It would probably be slightly more perfect if 1) the postinstall scripts
were run in a known order and 2) dependencies were tracked during local
Given the glacial progress of setup.exe development, I guess neither is
likely to happen soon.