This is the mail archive of the
mailing list for the Cygwin project.
Re: New Setup for Cygwin 1.7 on cygwin.com
On Wed, Aug 20, 2008 at 05:25:46PM +0200, Corinna Vinschen wrote:
>On Aug 20 11:17, Christopher Faylor wrote:
>> On Wed, Aug 20, 2008 at 04:46:30PM +0200, Corinna Vinschen wrote:
>> >On Aug 20 10:39, Christopher Faylor wrote:
>> >> On Wed, Aug 20, 2008 at 09:57:51AM +0200, Corinna Vinschen wrote:
>> >> >I removed all dependencies from release-2/base-passwd except for
>> >> >base-cygwin a couple of days ago. Hopefully we get to the point
>> >> >where the base packages' postinstalls run first.
>> >> Keeping a base-dependency in cygwin would make setup want to run base-*
>> >> before cygwin, though. Cygwin doesn't *really* depend on these packages
>> >> (it doesn't need them to run) so I don't think they should be a
>> >> dependency.
>> >That's the whole idea. Cygwin itself has no postinstall scripts, but
>> >the base-* scripts should run first. That's why the dependencies make
>> >sense. What else packages should depend on the base-* packages to
>> >accomplish this?
>> I thought the whole point was to install cygwin first. How can you run base
>> packages first in a new install when there is no cygwin1.dll?
>The installation order doesn't matter. Only the order in which scripts
>run matters. And I don't see another way how to make sure that the
>base-* scripts always run first.
AFAIK, the requires line controls the way that the packages themselves
are installed. I think it is important that the newest version of
cygwin should be installed first regardless of subsequent install script
processing. Maybe we need a dummy package to ensure the subsequent ordering
of post-install or we need a postinstall-requires?