This is the mail archive of the
mailing list for the Cygwin project.
Re: Parallel downloading of Cygwin packages
- From: paul dot hermeneutic at gmail dot com
- To: cygwin at cygwin dot com
- Date: Tue, 3 Nov 2009 10:25:14 -0600
- Subject: Re: Parallel downloading of Cygwin packages
- References: <4AEAD9EE.email@example.com> <20091030125852.GB1361@ednor.casa.cgf.cx> <4AEBA0D2.firstname.lastname@example.org> <20091031024002.GA19570@ednor.casa.cgf.cx> <4AEBBED1.email@example.com> <20091031152025.GA22041@ednor.casa.cgf.cx> <4AEE510F.firstname.lastname@example.org> <20091102134859.GC9072@ednor.casa.cgf.cx> <4AEFB41E.email@example.com>
On Mon, Nov 2, 2009 at 22:39, Chris Cormie <firstname.lastname@example.org> wrote:
> Christopher Faylor wrote:
>> On Mon, Nov 02, 2009 at 02:25:03PM +1100, Chris Cormie wrote:
>>>> There are barriers to implementing rpm in Cygwin, the most frequently
>>>> mentioned being the fact that a cygwin process can't easily replace
>>>> cygwin1.dll or any other running executables.
>>> If the in-Cygwin package manager can't update core Cygwin, that's not a
>>> deal breaker IMO: there is a fair bit of useful app package management that
>>> can be done without changing the core.
>> Maybe it's not clear but your personal needs are not really the issue
I thought that the standard Windows procedure was to create a run-once
to do the replacement after the machine is rebooted. Would that not
Yes, it would be much nicer to do things better than Microsoft, but
that is the current structure.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple