From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com, cygwin-developers@cygwin.com
Subject: Re: Updated: 1.7.0-34 (...and a plea)
Date: Tue, 09 Dec 2008 10:19:00 -0000 [thread overview]
Message-ID: <20081209102037.GE12905@calimero.vinschen.de> (raw)
In-Reply-To: <20081208195529.GB27323@ednor.casa.cgf.cx>
On Dec 8 14:55, Christopher Faylor wrote:
> On Mon, Dec 08, 2008 at 07:16:51PM +0100, Corinna Vinschen wrote:
> >On Dec 8 13:00, Christopher Faylor wrote:
> >> I think that when 1.7 is adopted
> >>
> >> release-2 -> release
> >> release -> release-deprecated
> >>
> >> and we make setup.exe changes to accommodate that.
> >
> >I was just going to agree but ... does that work? The idea is that
> >people still using an old setup will get the old release. Since
> >"release" is fixed in old versions of setup, it might be more feasible
> >to stick to release-2 or to use something along the lines you suggested
> >at one point, like, say, "release-nt".
>
> Ah, right. I wasn't thinking that people who had the old release might not
> want to update. Too bad we didn't have a mechanism in setup.exe to provide
> a warning to people before updating.
>
> So, release-2 becomes a first-class directory, setup.exe -> setup-deprecated.exe
> setup-1.7 -> setup.exe?
Sounds good to me.
Apropos package rebuild. The only package which really bugs me is the
orphaned cygwin-doc package. I guess I will havea try in rebuilding
a new one, even though I still don't get how to create the pdf docs.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2008-12-09 10:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 12:44 Updated: 1.7.0-33 (New method to logon without password ... with password) Corinna Vinschen
2008-12-05 11:07 ` Updated: 1.7.0-34 (...and a plea) Corinna Vinschen
2008-12-05 13:06 ` Chris Sutcliffe
2008-12-05 14:07 ` Corinna Vinschen
2008-12-05 17:00 ` Charles Wilson
2008-12-05 13:59 ` Eric Blake
2008-12-05 14:09 ` Corinna Vinschen
2008-12-08 17:02 ` Christopher Faylor
2008-12-08 17:15 ` Corinna Vinschen
2008-12-08 18:01 ` Christopher Faylor
2008-12-08 18:15 ` Corinna Vinschen
2008-12-08 19:56 ` Christopher Faylor
2008-12-09 10:19 ` Corinna Vinschen [this message]
2008-12-09 13:48 ` Corinna Vinschen
2008-12-09 14:47 ` Brian Dessent
2008-12-09 14:59 ` Corinna Vinschen
2008-12-09 15:02 ` Christopher Faylor
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=20081209102037.GE12905@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.com \
--cc=cygwin-developers@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).