[gentoo-portage-dev] building dependency tree

[Andrew Gaffney <agaffney@skylineaero.com>]

I am writing a Perl program that does the same thing as 'emerge'. Yes, I started 
a thread about this on -dev about 6 months back, but I'm better prepared to do 
this now. I've already written functions that:

   * Build a list of USE flags from /etc/make.profile/make.defaults, 
/etc/make.conf, and $ENV{USE}
   * Build a list of masked packages from /etc/make.profile/package.(un)mask and 
/etc/portage/package.(un)mask
   * Build a list of matching ebuild versions from a '>category/package-version' 
type string taking masked packages into account
   * Extract the DEPEND line from a particular ebuild
   * Parse a DEPEND line using active USE flags and build a list of needed packages

I'm starting work on the code that generates the actual dependency tree and then 
the list of packages to be installed. I don't have any Python skill, so I don't 
think that reading the code will help me much. Can anyone who deals with the 
Portage code a lot give me a general breakdown of the way that 'emerge' 
generates the dependency tree and then the list of packages to emerge?

-- 
Andrew Gaffney
Network Administrator
Skyline Aeronautics, LLC.
636-357-1548


--
gentoo-portage-dev@gentoo.org mailing list