public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin Ports)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: New Cygwin 1.7.0-18 in release-2
Date: Thu, 24 Jul 2008 16:18:00 -0000	[thread overview]
Message-ID: <4888AB1B.7000905@users.sourceforge.net> (raw)
In-Reply-To: <20080724092433.GE5251@calimero.vinschen.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Corinna Vinschen wrote:
| Honestly, I don't know.  Maybe it isn't.  But so far I'm still thinking
| that a parallel 1.7 install should only be a temporary solution for
| developers and maintainers.  It's not something I would like to drag
| on for years.  That's why an upgrade path has some merits for me.

I definitely agree that we don't want to support 1.5 anymore after 1.7
is stable.

| So far setup looks if c:\cygwin exists and if so, uses the install
| database in c:\cygwin\etc\setup accidentelly, even if you choose to
| install another installation to, say, D:\cygwin-2.

Would it suffice to rename /etc/setup/installed.db?


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkiIqxoACgkQpiWmPGlmQSPs+wCfbBHf8/82nFnMi0495IxmgZYH
9yYAoOIsocD8gruP4uyKhWWgCiDIPj7X
=DRzP
-----END PGP SIGNATURE-----

  reply	other threads:[~2008-07-24 16:18 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
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) [this message]
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=4888AB1B.7000905@users.sourceforge.net \
    --to=yselkowitz@users.sourceforge.net \
    --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).