Harry Putnam schreef:
> Holly Bostick <[EMAIL PROTECTED]> writes:
> 
>> Of course, you might want to upgrade to -r2, since clearly some 
>> things didn't work in -r1 (in ebuild terms)
>> 
>> You might also want to stick with stable until things settle down a
>>  bit.
>> 
> Holly, Thanks for the usual helpful effort.  Maybe you can tell me 
> how one controlls what ebuild is used.  For example:
<snip>
> I was able to to at least start mysql-5.0.15.ebuild, how would I 
> select it out of the others thru emerge?

Lots of ways-- to return to the stable build, try

# echo 'dev-db/mysql x86' >>/etc/portage/package.keywords

This will essentially change the ACCEPT_KEYWORDS setting for this
package only to stable. You may also have to add settings for the
dependencies, as they will still be unstable versions if you do not, and
I don't know how well the stable mysql build plays with the unstable
versions of its dependencies.

To only allow version 5.0.15, try

# echo '>dev-db/mysql-5.0.15' >>/etc/portage/package.mask

This will mask all unstable versions above 5.0.15. You will have to be
responsible for unmasking later versions when you feel that they have
stabilized to your needs (meaning, you have to keep an eye on the status
of the ebuilds, because even when later versions go stable, you won't
have them available to you in Portage).

So I would almost say go back to stable, and when the currently unstable
upgrades become stable, just upgrade normally. Unless you have some
burning reason to have version 5 now, today, no matter what the
circumstances.
> 
> I foolishly ran the last -u world with ACCEPT_KEYWORDS=~x86 and have
>  since set that globally.  So I'm now bleeding edge and it appears 
> that it would take some doing to undo that at this point so thought 
> I'd go with it for a while and see if I could get ontop of it.
> 
> I know about using the actual path and that is how I'm installing it
>  as I write but one always gets those troublesome messages about 
> installing by path being broken....


Ummmm.... no you don't so much need to use the actual path as you need
to use the correct syntax to emerge a particular version of a package:

emerge =dev-db/mysql-5.0.15

or emerge (<=>)[= - the exact version; >= - any version greater than or
equal to; <= - any version less than or equal to; > - any version
greater than; < - any version less than]cate-gory/package-version.number

Naturally if you do something like this, though, you'll want to utilize
package.mask to block other versions so that Portage doesn't try to
upgrade or downgrade the package you've specifically emerged in a
particular version.


HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list

Reply via email to