From: Enrico Weigelt <weigelt@metux.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: world favorites: pros and cons
Date: Mon, 7 Aug 2006 18:53:05 +0200 [thread overview]
Message-ID: <20060807165304.GC8026@nibiru.local> (raw)
In-Reply-To: <20060728133011.1b8e6374@sed-192.sedsystems.ca>
* Jim Ramsay <i.am@jimramsay.com> wrote:
<snip>
> Then you could do:
>
> >=dev-db/mysql-4.2
>
> This would allow any mysql-4.1.*, including 4.1.20-r1 and 4.1.99
>
> Though you do raise a good point... it would be nice to specify a "real
> upstream version number" differently from the Gentoo "interim release
> number" such as -r2. Can you think of a sane way to do that?
Simply normalize the version numbers to a fixed amount of digit
and use another one for gentoo's revisions ?
I'm using 4 digits at my own buildsystem, but sometimes the upstream
requires them all for itself, so we need some more, ie. 6
<snip>
> Masking
> >dev-db/mysql-4.1.20+
> should allow mysql-4.1.20-r1 but not mysql-4.1.21
"=dev-db/mysql-4.1.20.*" seems to be cleaner to me.
Maybe
"=dev-db/mysql-4.2.20" could be considered equal.
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-07 17:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 9:48 [gentoo-user] world favorites: pros and cons Daniel
2006-07-05 10:10 ` Neil Bothwick
2006-07-05 10:21 ` Alexander Skwar
2006-07-05 10:18 ` Alexander Skwar
2006-07-05 10:55 ` Neil Bothwick
2006-07-05 11:11 ` Daniel
2006-07-05 11:33 ` Rumen Yotov
2006-07-05 11:54 ` Daniel Iliev
2006-07-05 12:14 ` Neil Bothwick
2006-07-05 12:43 ` Daniel Iliev
2006-07-05 13:16 ` Alexander Skwar
2006-07-05 14:47 ` Alan McKinnon
2006-07-05 13:21 ` Neil Bothwick
2006-07-05 14:29 ` Daniel Iliev
2006-07-05 15:08 ` Neil Bothwick
2006-07-05 16:53 ` Daniel Iliev
2006-07-05 20:15 ` Neil Bothwick
2006-07-05 16:38 ` Richard Fish
2006-07-05 17:10 ` Daniel Iliev
2006-07-05 18:15 ` Richard Fish
2006-07-05 18:59 ` Daniel Iliev
2006-07-05 19:47 ` Richard Fish
2006-07-05 16:54 ` Daniel da Veiga
2006-07-05 18:30 ` Daniel Iliev
2006-07-05 19:17 ` Daniel da Veiga
2006-07-05 20:01 ` Daniel Iliev
2006-07-28 18:30 ` Enrico Weigelt
2006-07-28 18:46 ` [gentoo-user] " Jim Ramsay
2006-07-28 18:57 ` Alexander Skwar
2006-07-28 19:10 ` Enrico Weigelt
2006-07-28 19:30 ` Jim Ramsay
2006-07-28 20:39 ` Daniel da Veiga
2006-07-28 21:03 ` Jim Ramsay
2006-07-28 21:03 ` Jim Ramsay
2006-08-07 16:53 ` Enrico Weigelt [this message]
2006-07-05 22:27 ` [gentoo-user] " Daniel Iliev
2006-07-05 22:43 ` Ryan Tandy
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=20060807165304.GC8026@nibiru.local \
--to=weigelt@metux.de \
--cc=gentoo-user@lists.gentoo.org \
/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