Hi,
Bo Ørsted Andresen [EMAIL PROTECTED] writes:
On Friday 24 August 2007 18:24:33 David Bonnafous wrote:
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)
I didn't quite understand what this question is about.
Are you trying to figure out why that dependency were added?
No I am not trying to figure out why that dependency were added. I
think the gentoo developers have good reasons to do that in that way.
After a sync (see below what and how) when I try to re-merge a package
(same version) and emerge tell me that there is a dependency not
satified I would like to know where this dependency come from. Because
this is a new dependency, added after the sync by
- a mistake I do (wrong /etc/portage/package.mask)
- a minor revison (new CVS version) of a ebuild not so minor
- a modification of a eclass
And my question is how to know is this new dependency comme from
eclass, or more generaly what are the dependencies that come from
eclass ?
What do you intend to do with this overlay?
I intend to be able to maintain for a long time a set of package
(ebuild and files) I use on my servers. I want to be able to recompile
them as I need even if gentoo developers remove them from the official
portage tree.
Why do you sync at all?
In fact I have added --backup --backup-dir='/usr/local/portage' to
the rsync options. Then after a sync I have in /usr/local/portage all
the files that changed. So I clean up this tree (remove eclass
directory, redundant package ebuild,...).
Yours,
--
Bo Andresen
--
David Bonnafous
Institut de Mathématiques
Université Paul Sabatier
Toulouse - France
--
[EMAIL PROTECTED] mailing list
