From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: upset, genini: different version ordering
Date: Tue, 21 Jul 2015 18:49:00 -0000 [thread overview]
Message-ID: <20150721184914.GE3864@calimero.vinschen.de> (raw)
In-Reply-To: <87r3o1phtw.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
On Jul 21 18:59, Achim Gratz wrote:
> Corinna Vinschen writes:
> > How do you tell upset that a package uses a different numbering
> > scheme? You'd have two scenarios which can't be recognized
> > automatically, don't you?
>
> In the case of Perl distributions, I know the ordering scheme and it's
> built in to upset already, sort-of, only has to be used. For the rest
> upset should probably keep doing what it was doing before, but I want to
> fix genini to do the same.
>
> In the long run we might want to add some keyword in setup.hint that
> specifies which ordering algorithm to use.
That's not sufficient, probably. I'm pretty sure you'd have to tweak
setup as well.
And then there's still the questionable license of upset...
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-21 18:49 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 18:03 Achim Gratz
2015-07-20 18:10 ` Jon TURNEY
2015-07-20 18:42 ` Achim Gratz
2015-07-20 19:00 ` Corinna Vinschen
2015-07-20 20:09 ` Achim Gratz
2015-07-21 6:56 ` Corinna Vinschen
2015-07-21 16:59 ` Achim Gratz
2015-07-21 18:49 ` Corinna Vinschen [this message]
2015-07-21 19:13 ` Achim Gratz
2015-07-22 9:43 ` Corinna Vinschen
2015-07-22 16:21 ` Achim Gratz
2015-07-23 9:59 ` Corinna Vinschen
2015-07-23 17:09 ` Achim Gratz
2015-07-23 19:17 ` Corinna Vinschen
2015-07-23 19:29 ` Corinna Vinschen
2015-07-23 19:38 ` Achim Gratz
2015-07-23 19:51 ` Corinna Vinschen
2015-07-23 20:02 ` Achim Gratz
2015-07-24 9:19 ` Corinna Vinschen
2015-07-24 18:09 ` Achim Gratz
2015-07-24 18:16 ` Achim Gratz
2015-10-09 13:24 ` Jon Turney
2015-10-19 15:42 ` Corinna Vinschen
2015-10-19 17:19 ` Achim Gratz
2015-10-19 17:28 ` Yaakov Selkowitz
2015-10-19 18:13 ` Achim Gratz
2015-10-20 10:27 ` Corinna Vinschen
2015-10-20 13:33 ` Jon Turney
2015-10-20 15:50 ` Corinna Vinschen
2015-10-20 17:03 ` Yaakov Selkowitz
2015-10-20 19:18 ` Corinna Vinschen
2015-10-20 19:53 ` Achim Gratz
2015-10-20 20:35 ` Yaakov Selkowitz
2015-10-21 16:45 ` Achim Gratz
2015-10-21 17:04 ` Yaakov Selkowitz
2015-11-20 19:14 ` Jon Turney
2015-10-20 13:47 ` Jon Turney
2015-10-20 17:29 ` Achim Gratz
2015-08-18 18:34 ` Achim Gratz
2015-08-18 19:06 ` Corinna Vinschen
2015-08-18 20:07 ` Achim Gratz
2015-08-19 8:25 ` Corinna Vinschen
2015-08-21 13:28 ` Corinna Vinschen
2015-08-21 18:35 ` Achim Gratz
2015-08-22 10:48 ` Achim Gratz
2015-08-22 10:51 ` Achim Gratz
2015-08-22 13:29 ` Corinna Vinschen
2015-08-22 15:11 ` Achim Gratz
2015-08-24 7:27 ` Corinna Vinschen
2015-09-03 16:34 ` Corinna Vinschen
2015-08-20 11:37 ` Jon TURNEY
2015-08-20 19:55 ` Achim Gratz
2015-08-24 11:25 ` Yaakov Selkowitz
2015-08-24 12:29 ` Corinna Vinschen
2015-08-24 17:13 ` Achim Gratz
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=20150721184914.GE3864@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).