Apologies if this is a FAQ or something. I've looked around, honest. I'm looking for a way of preventing entropy from wanting to downgrade packages that I've installed via portage. For example, I'm using kdenlive ( a video editing app ), and according to kdenlive devs, libsdl-1.2.13 is quite buggy and not good at all for kdenlive users. So I've installed 1.2.14 via portage. Also I've built various X libs, mesa, ati drivers, etc, for my r600 card ( it's working great with KMS and DRI2 by the way ).
I know about and have set:
- Code: Select all
in /etc/entropy/client.conf ... but this only prevents downgrading packages with a -9999 version number. It doesn't help with my libsdl example.
To make things more complicated ... I understand that some library upgrades ( eg libsdl ) require rebuilding things that are linked against them. So I can see that the simple option of just ignoring entropy's dependency requirements could lead to broken packages, with some software installed that is expecting libsdl-1.2.13, but instead finding libsdl-1.2.14. Curse the people who break binary compatibility with minor version bumps!
So what might help out is a way to tell entropy to ignore some packages completely ... a bit like /etc/portage/packages.mask. This way I could use portage to rebuild anything that depends on libsdl that I've just upgraded, and entropy wouldn't try to undo my work.
Is this possible?