| 1 |
Holly Bostick <motub@××××××.nl> writes: |
| 2 |
|
| 3 |
|
| 4 |
[...] good info |
| 5 |
|
| 6 |
> Of course, you might want to upgrade to -r2, since clearly some things |
| 7 |
> didn't work in -r1 (in ebuild terms) |
| 8 |
> |
| 9 |
> You might also want to stick with stable until things settle down a bit. |
| 10 |
> |
| 11 |
> Just my 2 Eurocents, as you see, I'm not a MySQL user. |
| 12 |
|
| 13 |
Holly, |
| 14 |
Thanks for the usual helpful effort. Maybe you can tell me how one |
| 15 |
controlls what ebuild is used. For example: |
| 16 |
|
| 17 |
ls /usr/portage/dev-db/mysql |
| 18 |
ChangeLog mysql-4.0.25-r2.ebuild mysql-5.0.15.ebuild |
| 19 |
Manifest mysql-4.0.26.ebuild mysql-5.0.16-r1.ebuild |
| 20 |
files mysql-4.1.14.ebuild mysql-5.0.16-r30.ebuild |
| 21 |
metadata.xml mysql-4.1.15-r30.ebuild |
| 22 |
mysql-3.23.58-r1.ebuild mysql-4.1.15.ebuild |
| 23 |
|
| 24 |
I was able to to at least start mysql-5.0.15.ebuild, how would I |
| 25 |
select it out of the others thru emerge? |
| 26 |
|
| 27 |
I foolishly ran the last -u world with ACCEPT_KEYWORDS=~x86 and have |
| 28 |
since set that globally. So I'm now bleeding edge and it appears that |
| 29 |
it would take some doing to undo that at this point so thought I'd go |
| 30 |
with it for a while and see if I could get ontop of it. |
| 31 |
|
| 32 |
I know about using the actual path and that is how I'm installing it |
| 33 |
as I write but one always gets those troublesome messages about |
| 34 |
installing by path being broken.... |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-user@g.o mailing list |
Archives