On Friday 24 August 2007, David Bonnafous wrote:
> hi,
>
> I'm working to get a "stable portage overlay" to keep ebuild and
> files I used to build my system.
>
> But even if I keep the ebuild and all the files needed, the command
> "emerge --sync" introduces some dependencies by modifying eclass.
>
> How can I know (localize) this kind of dependencies ?
>
> I found the first one using grep
>
> JAVA_PKG_PORTAGE_DEP=">=sys-apps/portage-2.1.2.7"
>
> in eclass/java-utils-2.eclass (change from version 1.91 to 1.92)
Sounds like you want to keep the old eclass around inside the overlay
and let portage update ${PORTDIR}/eclass/* as it sees fit?
I have this setup, I simply created an eclass directory in my overlay
directory, added the ebuild to the overlay, and the ebuilds started
using the overlay version of the eclass. Something like:
/var/portage/local/alan/eclass/ is where I put my eclasses.
--
Optimists say the glass is half full,
Pessimists say the glass is half empty,
Developers say wtf is the glass twice as big as it needs to be?
Alan McKinnon
alan at linuxholdings dot co dot za
+27 82, double three seven, one nine three five
--
[EMAIL PROTECTED] mailing list
