public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: "John Morrison" <john@morrison.mine.nu>
To: cygwin-apps@cygwin.com
Subject: Re: New Cygwin 1.7.0-18 in release-2
Date: Wed, 23 Jul 2008 20:44:00 -0000	[thread overview]
Message-ID: <394fb80db854e1eefd91bf014c162a24.squirrel@mail.morrison.mine.nu> (raw)
In-Reply-To: <20080723180000.GA5251@calimero.vinschen.de>

On Wed, July 23, 2008 7:00 pm, Corinna Vinschen wrote:
> On Jul 23 12:25, Yaakov (Cygwin Ports) wrote:
>> Corinna Vinschen wrote:
>> | When 1.7 goes gold, the idea is to install over an 1.5 install.  Or
>> not.
>> | It's the choice of the user.
>>
>> The advantage of "starting fresh" with 1.7 would allow us to dump a lot
>> of obsolete packages from the distro [...]
>> but IMHO everything should anyways be rebuilt for 1.7.
>
> I'd be happy if even the most important packages have been rebuilt for
> 1.7.  So far the reactions from the package maintainers were somewhat
> reticent.

I think that'll probably alter once there's a setup for 1.7.  Speaking
personally I *need* my installation of cygwin and couldn't stand to be
without it.  (I will get 'round to patching the base packages, but I
was/did hand these over to Igor; is he still around?)

X under 1.7 is a requirement for me.  Just wish I had the skills to get
the latest version working.

>> OTOH I'm not sure what the user reaction would be.  I suppose one
>> compromise would be to require users to "rm -fr /etc/setup" before
>> upgrading to 1.7.

Once X works, that works for me :)

> I'm still rather trying to smooth out the upgrade path so that there
> are as little as possible manual changes left to the user.  It will
> be bumpy nevertheless...
>
>> | There's no roadmap.  What's missing for a release is
>> |
>> | - A new setup.exe
>> |
>> | - The Cygwin utils are not quite up to speed
>> |
>> | - Documentation changes
>> |
>> | - Support by the package maintainers
>> |
>> | - Testing
>> |
>> | All of the above items could need a helping hand.  If 1.7 isn't too
>> | buggy, I plan to release 1.7 still in 2008.  When that actually
>> happens
>> | doesn't depend on me.  Cygwin 1.7 development has gone on for two
>> years
>> | and it comes with a lot of changes.  Not all of them allow a 100%
>> smooth
>> | transition.
>> | Eventually this release depends on the support it gets from all of
>> you.
>>
>> I for one would like to "catch up" the distro to what I've made
>> available in Ports.
>
> Cool.

Definately.

>> Could someone point me again to the current directions to install 1.7 in
>> parallel to 1.5 on the same machine?
>
> The problem so far is the "Cygnus Solutions" registry key and the
> default name of the cygwin dir, C:\cygwin.  When you try to install
> 1.7, both shouldn't exist.  So what I did is this:
>
> - Rename C:\cygwin to C:\cygwin-1.5.  Change this everywhere in the
>   registry.
>
> - My HKCU "Cygnus Solutions" mount table is empty anyway, so it doesn't
>   matter.  Rename HKLM "Cygnus Solutions" to "Cygnus Solutions 1.5".
>
> - Install Cygwin 1.7 with setup-1.7.exe into C:\cygwin.
>
> - Rename HKLM "Cygnus Solutions" to "Cygnus Solutions 1.7"
>
> - Rename HKLM "Cygnus Solutions 1.5" back to "Cygnus Solutions".
>
> Since 1.7 doesn't use the above registry key, it doesn't matter for
> running 1.7.  Just when calling setup-1.7 for an update, the registry
> key rename orgy starts again.
>
> We *really* need a new setup for 1.7 which doesn't access the "Cygnus
> Solutions" registry key anymore.

Agreed :(

J.

(attempting to find some time!)

  reply	other threads:[~2008-07-23 20:44 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 15:53 Corinna Vinschen
2008-07-18  0:18 ` Eric Blake
2008-07-18  7:33   ` Corinna Vinschen
2008-07-18  7:53     ` Corinna Vinschen
2008-07-18  8:08       ` Corinna Vinschen
2008-07-18 12:07         ` Corinna Vinschen
2008-07-22 21:19           ` Corinna Vinschen
2008-07-18 16:37 ` Marco Atzeri
2008-07-18 17:08   ` Corinna Vinschen
2008-07-18 17:56     ` Christopher Faylor
2008-07-18 18:18       ` Corinna Vinschen
2008-07-18 23:59         ` Brian Dessent
2008-07-19 10:15         ` Marco Atzeri
2008-07-18 19:29 ` Bill Hoffman
2008-07-19 12:24   ` Corinna Vinschen
2008-07-19 14:16 ` Cygwin 1.7.0-19 (was Re: New Cygwin 1.7.0-18 in release-2) Corinna Vinschen
2008-07-22 17:42   ` Cygwin 1.7.0-20 (was Re: Cygwin 1.7.0-19 (was Re: New Cygwin 1.7.0-18 in release-2)) Corinna Vinschen
2008-07-25  8:10     ` Corinna Vinschen
2008-07-25 11:00       ` 1.7.0-21 broken Corinna Vinschen
2008-07-25 18:08         ` Corinna Vinschen
2008-07-28 14:52     ` base-[files|password] for 1.7 (was Re: Cygwin 1.7.0-20 (was Re: Cygwin 1.7.0-19 (was Re: New Cygwin 1.7.0-18 in release-2))) John Morrison
2008-07-28 15:27       ` Corinna Vinschen
2008-07-28 16:34         ` base-[files|password] for 1.7 John Morrison
2008-07-29  9:32           ` Corinna Vinschen
2008-07-29 11:50             ` Eric Blake
2008-07-28 18:56         ` Pierre A. Humblet
2008-07-29  9:45           ` Corinna Vinschen
2008-07-29 14:35             ` Pierre A. Humblet
2008-07-29 14:53               ` Corinna Vinschen
2008-07-29 16:24                 ` Pierre A. Humblet
2008-07-29 22:22                   ` Pierre A. Humblet
2008-07-30  9:14                     ` Corinna Vinschen
2008-07-28 19:00         ` base-[files|password] for 1.7 (was Re: Cygwin 1.7.0-20 (was Re: Cygwin 1.7.0-19 (was Re: New Cygwin 1.7.0-18 in release-2))) Christopher Faylor
2008-07-29 11:37         ` Eric Blake
2008-07-29 11:56           ` John Morrison
2008-07-29 12:01             ` base-[files|password] for 1.7 Eric Blake
2008-07-29 12:28               ` Corinna Vinschen
2008-07-29 14:31                 ` Christopher Faylor
2008-07-29 14:56                   ` Corinna Vinschen
2008-07-29 16:18                     ` John Morrison
2008-07-29 18:00                       ` Christopher Faylor
2008-07-30  1:39                         ` Christopher Faylor
2008-07-30  9:22                           ` Corinna Vinschen
2008-07-30 15:20                             ` Christopher Faylor
2008-07-30 17:39                               ` Corinna Vinschen
2008-07-21 23:42 ` New Cygwin 1.7.0-18 in release-2 Yaakov (Cygwin Ports)
2008-07-22  9:32   ` Corinna Vinschen
2008-07-23 17:26     ` Yaakov (Cygwin Ports)
2008-07-23 18:00       ` Corinna Vinschen
2008-07-23 20:44         ` John Morrison [this message]
2008-07-24  9:08           ` Corinna Vinschen
2008-07-24  9:18             ` John Morrison
2008-07-24  9:26               ` Corinna Vinschen
2008-07-25 10:07           ` Andrew Schulman
2008-07-24  3:45         ` Yaakov (Cygwin Ports)
2008-07-24  9:24           ` Corinna Vinschen
2008-07-24 16:18             ` Yaakov (Cygwin Ports)
2008-07-24 17:46               ` Corinna Vinschen
2008-07-31  6:57 ` Yaakov (Cygwin Ports)
2008-07-31  7:39   ` Corinna Vinschen
2008-07-31  8:28     ` Yaakov (Cygwin Ports)
2008-07-31 11:44       ` Corinna Vinschen
2008-07-31 13:00         ` Charles Wilson
2008-07-31 13:23           ` Corinna Vinschen
2008-07-31 13:31             ` Corinna Vinschen
2008-07-31 14:10               ` Corinna Vinschen
2008-07-31 20:16                 ` Corinna Vinschen
2008-07-31 15:06         ` Yaakov (Cygwin Ports)
2008-07-31 15:41           ` Corinna Vinschen

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=394fb80db854e1eefd91bf014c162a24.squirrel@mail.morrison.mine.nu \
    --to=john@morrison.mine.nu \
    --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).