From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Changing dependent library version numbers vs. test packages vs. requires: lines.
Date: Sat, 24 Nov 2012 09:48:00 -0000 [thread overview]
Message-ID: <20121124094756.GZ17347@calimero.vinschen.de> (raw)
In-Reply-To: <50B0611C.4090300@gmail.com>
On Nov 24 06:54, marco atzeri wrote:
> On 11/23/2012 6:17 PM, Dave Korn wrote:
> >
> > Hi all,
> >
> > I've got a gcc-4.7.2 package almost ready to upload, but there's one issue
> >I'm not sure what's best to do about.
> >
> > Several of the runtime libs have changed version numbers, i.e.
> >libgnat4.5->libgnat4.7, libgcj11->libgcj13, libobjc2->libobjc4.
> >
> > I'd like to release a test: version of the new compiler, but I don't know
> >what's best to do for the requires: lines in the setup hint files.
> >
> > If I add the new library versions, those dependencies will also be pulled in
> >by people installing the curr: version of the compiler, but the new libraries
> >won't exist in curr: versions.
> >
> > If I don't, people installing the test: version will have to ensure they
> >manually select the new runtime libraries, which might be the least worst option.
> >
> > Is there any better way to handle this situation?
> >
> > cheers,
> > DaveK
> >
>
> I doubt until someone changes setup.
> Put all the dependencies on your Announce, who want to try should be
> able to install them.
>
> Marco
ACK.
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:[~2012-11-24 9:48 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 17:16 Dave Korn
2012-11-24 5:54 ` marco atzeri
2012-11-24 9:48 ` Corinna Vinschen [this message]
2013-01-14 16:50 ` Chris Sutcliffe
2013-01-18 13:32 ` Corinna Vinschen
2013-02-04 10:17 ` Corinna Vinschen
2013-02-18 23:59 ` Chris Sutcliffe
2013-02-19 7:46 ` GCC maintainer volunteer? (was Re: Changing dependent library version numbers vs. test packages vs. requires: lines.) Corinna Vinschen
2013-02-19 10:22 ` JonY
2013-02-19 11:46 ` Yaakov
2013-02-19 12:53 ` JonY
2013-02-21 11:53 ` JonY
2013-02-21 12:40 ` NightStrike
2013-02-21 13:34 ` GCC maintainer volunteer? JonY
2013-02-21 13:42 ` Corinna Vinschen
2013-02-21 13:47 ` JonY
2013-02-21 15:39 ` NightStrike
2013-02-21 16:31 ` Chris Sutcliffe
2013-02-21 16:59 ` Corinna Vinschen
2013-02-21 21:48 ` JonY
2013-02-21 23:48 ` marco atzeri
2013-02-22 5:21 ` Christopher Faylor
2013-02-22 8:39 ` Corinna Vinschen
2013-02-22 7:31 ` Yaakov
2013-02-22 8:38 ` Corinna Vinschen
2013-02-22 9:18 ` JonY
2013-02-23 15:04 ` JonY
2013-02-23 15:46 ` Ken Brown
2013-02-24 1:12 ` JonY
2013-02-24 1:39 ` Ken Brown
2013-02-24 2:02 ` JonY
2013-02-24 4:55 ` Christopher Faylor
2013-02-24 5:22 ` Chris Sutcliffe
2013-02-25 14:40 ` JonY
2013-02-25 18:22 ` Christopher Faylor
2013-02-27 12:06 ` JonY
2013-02-27 13:11 ` Corinna Vinschen
2013-02-27 13:29 ` JonY
2013-02-27 13:59 ` Corinna Vinschen
2013-02-27 22:24 ` JonY
2013-02-28 0:28 ` marco atzeri
2013-02-28 10:05 ` Yaakov
2013-02-28 17:06 ` NightStrike
2013-02-28 19:44 ` Yaakov
2013-03-06 10:29 ` Yaakov
2013-03-06 10:41 ` Corinna Vinschen
2013-03-06 16:14 ` 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=20121124094756.GZ17347@calimero.vinschen.de \
--to=corinna-cygwin@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).