| 1 |
On Mon, 18 Jul 2005, Mauro Faccenda wrote: |
| 2 |
|
| 3 |
> Dmitry S. Makovey wrote: |
| 4 |
>> For past couple of weeks as I was doing emerge --sync and emerge -uDNp |
| 5 |
>> I've noticed that libgsf has "jumping" versions. That is one week |
| 6 |
>> it's 1.12.0 another 1.10.0 and it swings from one to another. Does |
| 7 |
>> anybody know what might trigger this behavior? |
| 8 |
>> |
| 9 |
> |
| 10 |
> This is because gnumeric REQUIRES =1.10.0... and when you do a -uD it |
| 11 |
> will be upgraded. |
| 12 |
> |
| 13 |
> You should keep using -uNp instead of -uDNp ;) |
| 14 |
|
| 15 |
I wouldn't throw away -uDNp just because of this. |
| 16 |
|
| 17 |
On my system there are only two packages that depend on libgsf: |
| 18 |
|
| 19 |
gnumeric =gnome-extra/libgsf-1.10* |
| 20 |
librsvg >=gnome-extra/libgsf-1.6 |
| 21 |
|
| 22 |
So librsvg can survive with an libgsf version as old as 1.6. |
| 23 |
|
| 24 |
My solution has been adding these lines to /etc/portage/package.mask: |
| 25 |
=gnome-extra/libgsf-1.12.0 |
| 26 |
=gnome-extra/libgsf-1.12.1 |
| 27 |
|
| 28 |
Ofcourse I could also use >=gnome-extra/libgsf-1.12.0, but I prefer to be |
| 29 |
notified if there is a new version available. |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
T.G. |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives