From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] 1.7 Packaging: Obsolete packages
Date: Fri, 25 Jul 2008 16:13:00 -0000 [thread overview]
Message-ID: <20080725161259.GC10812@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20080725151630.GW5251@calimero.vinschen.de>
On Fri, Jul 25, 2008 at 05:16:30PM +0200, Corinna Vinschen wrote:
>On Jul 25 10:52, Christopher Faylor wrote:
>> On Fri, Jul 25, 2008 at 11:40:34AM +0200, Corinna Vinschen wrote:
>> >Nice example. Still, for now we should assume that we go the upgrade
>> >path. I'm going to investigate the impact of a clean cut in the next
>> >couple of days.
>>
>> It seems like maybe another change to setup.exe would be in order here
>> or maybe there could be a base package which did any cleanup required to
>> purge unneeded packages.
>
>Another base package sounds like an interesting idea. OTOH, setup would
>use the existing local setup database and might get something wrong
>before the new base package has a chance to do the cleanup. Baah.
>Maybe we could provide an upgrade helper script which should run *before*
>running setup for the ultimate upgrade.
I was thinking of a variation of _update_info which waited until everything
was done before it started doing anything. You could even write a mingw
app which didn't rely on cygwin to do some of the work.
cgf
next prev parent reply other threads:[~2008-07-25 16:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 4:44 Yaakov (Cygwin Ports)
2008-07-24 9:43 ` Corinna Vinschen
2008-07-24 23:44 ` Yaakov (Cygwin Ports)
2008-07-25 9:40 ` Corinna Vinschen
2008-07-25 14:53 ` Christopher Faylor
2008-07-25 15:16 ` Corinna Vinschen
2008-07-25 16:13 ` Christopher Faylor [this message]
2008-07-28 2:20 ` Yaakov (Cygwin Ports)
2008-07-28 8:45 ` Corinna Vinschen
2008-07-28 16:40 ` Brian Dessent
2008-07-30 12:17 ` Corinna Vinschen
2008-07-30 15:01 ` Yaakov (Cygwin Ports)
2008-07-30 15:25 ` Christopher Faylor
2008-08-21 4:22 ` Yaakov (Cygwin Ports)
2008-08-21 8:24 ` Corinna Vinschen
2008-08-21 10:34 ` Corinna Vinschen
2008-08-21 11:45 ` Corinna Vinschen
2008-08-22 1:30 ` Brian Dessent
2008-08-22 8:18 ` Corinna Vinschen
2008-08-22 8:53 ` Brian Dessent
2008-08-22 9:12 ` Brian Dessent
2008-08-22 9:23 ` Corinna Vinschen
2008-08-22 9:30 ` Brian Dessent
2008-08-22 10:11 ` Corinna Vinschen
2008-08-22 10:54 ` Brian Dessent
2008-08-25 10:27 ` Corinna Vinschen
2008-08-22 9:26 ` Brian Dessent
2008-08-22 11:25 ` Charles Wilson
2008-08-21 23:47 ` Yaakov (Cygwin Ports)
2008-07-25 19:31 ` Nicholas Wourms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080725161259.GC10812@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).