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 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:
>> >On Aug 19 22:46, Christopher Faylor wrote:
>> >> On Tue, Aug 19, 2008 at 06:48:44PM -0700, Brian Dessent wrote:
>> >> >Can we special-case upset not to add _update-info-dir to the Cygwin
>> >> >package?
>> >> I'm not a big fan of special casing and in this case I don't have to.
>> >> I just added a "noautodep: _update_info_dir" to cygwin's setup.hint.
>> >Cool. I'm curious how this changes the dependency order.
>> >> But we'll still get a dependency loop with base-passwd. I have removed
>> >> that dependency in release. It looks like this isn't needed in
>> >> release-2.
>> >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
>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
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?