Re: [gentoo-user] Re: world favorites: pros and cons
* Jim Ramsay [EMAIL PROTECTED] 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
Re: [gentoo-user] Re: world favorites: pros and cons
Jim Ramsay schrieb: Enrico Weigelt wrote: * Daniel da Veiga [EMAIL PROTECTED] wrote: Also, the world file is a simple way to keep a package version (by removing it from world), for instance, I don't wanna upgrade mysql with my nightly emerge -uDN world, so, its not in my world file. Isn't there any way for nailing it down to some specific version ? Sure, mask anything higher than the version you want in your /etc/portage/package.mask file: dev-db/mysql-4.1.20 And then put the ebuild you're using into a local overlay. Reason: Sooner or later, the package might/will be dropped (as it's too old) but you'll still need the ebuild. Alexander Skwar -- I'm not a god, I was misquoted. -- Lister, Red Dwarf -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: world favorites: pros and cons
* Alexander Skwar [EMAIL PROTECTED] wrote: snip Sure, mask anything higher than the version you want in your /etc/portage/package.mask file: dev-db/mysql-4.1.20 And then put the ebuild you're using into a local overlay. Reason: Sooner or later, the package might/will be dropped (as it's too old) but you'll still need the ebuild. Yeah, but this would also prevent fixes in this ebuild. (ie. if there's a typo or broken dependency) 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
Re: [gentoo-user] Re: world favorites: pros and cons
On 7/28/06, Jim Ramsay [EMAIL PROTECTED] wrote: Enrico Weigelt wrote: Yeah, but this would also prevent fixes in this ebuild. (ie. if there's a typo or broken dependency) 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? My suggestion would be to use a '+' character to represent all possible gentoo interim releases, as follows: Masking dev-db/mysql-4.1.20+ should allow mysql-4.1.20-r1 but not mysql-4.1.21 Take a look at the ~ operator... -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- gentoo-user@gentoo.org mailing list
