From: Andrew Gaffney <agaffney@skylineaero.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] building dependency tree
Date: Sat, 15 May 2004 10:31:41 -0500 [thread overview]
Message-ID: <40A637DD.70700@skylineaero.com> (raw)
In-Reply-To: <200405151606.37771.jstubbs@gentoo.org>
Jason Stubbs wrote:
> On Saturday 15 May 2004 15:50, Andrew Gaffney wrote:
>
>>>Jason Stubbs wrote:
>>>
>>>>On Saturday 15 May 2004 13:12, Andrew Gaffney wrote:
>>>>
>>>>>>You've already done a complete rewrite of the dependency resolver?
>>>>
>>>>Yes and no. I started from scratch but used almost exactly the same
>>>>logic. I guess you could almost call it refactoring. Have a look at:
>>>>http://www.gentoo.org/cgi-bin/viewcvs.cgi/portage-mod/portageapi/?root=ge
>>>>ntoo-src
>>>>
>>>>Of interest to you, will probably be dep.py. Even if you do not
>>>>understand python, the logic should be fairly clear (I hope!). The only
>>>>real change from the above logic is that installed packages (including
>>>>their original USE flags and *DEPENDs) are also taken into account.
>>>
>>>I'll have to take a look at it. If anyone wants to take a look at my code
>>>(and maybe give me a few suggestions), the (almost) latest working version
>>>can be accessed at <http://locutus.homeip.net/dev/portage.pl>. It currently
>>>operates the same way 'emerge -ep' would. It doesn't generate the exact
>>>same packages to install as Portage, but it is pretty damn close.
>
> May I ask what you are writing this for? Once the API I'm working on is
> completed, tested and integrated (<2 months?) I'll start working on wrappers
> for other languages. Is that the sort of thing you are after?
I'm not quite sure why I'm doing it. Partly, I wanted to see if I could write a
program that is faster than Portage. I also like to really understand how things
work "under the hood". Writing a Perl program that functions like Portage's has
really helped me do this.
--
Andrew Gaffney
Network Administrator
Skyline Aeronautics, LLC.
636-357-1548
--
gentoo-portage-dev@gentoo.org mailing list
prev parent reply other threads:[~2004-05-15 15:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 3:02 [gentoo-portage-dev] building dependency tree Andrew Gaffney
2004-05-12 5:14 ` Pieter Van den Abeele
2004-05-12 6:42 ` Andrew Gaffney
2004-05-12 7:59 ` Pieter Van den Abeele
2004-05-12 14:43 ` Andrew Gaffney
2004-05-12 15:02 ` Pieter Van den Abeele
2004-05-12 15:14 ` [gentoo-portage-dev] /etc/make.profile/use.defaults (was: building dependency tree) Andrew Gaffney
2004-05-12 15:19 ` [gentoo-portage-dev] /etc/make.profile/use.defaults Andrew Gaffney
2004-05-12 15:43 ` Pieter Van den Abeele
2004-05-12 15:44 ` Andrew Gaffney
2004-05-12 16:03 ` Pieter Van den Abeele
2004-05-12 16:08 ` Andrew Gaffney
2004-05-12 16:33 ` Jason Stubbs
2004-05-12 16:39 ` Andrew Gaffney
2004-05-12 17:28 ` Jason Stubbs
2004-05-12 16:25 ` [gentoo-portage-dev] building dependency tree Jason Stubbs
2004-05-15 4:12 ` Andrew Gaffney
2004-05-15 6:14 ` Jason Stubbs
2004-05-15 6:50 ` Andrew Gaffney
2004-05-15 7:06 ` Jason Stubbs
2004-05-15 15:31 ` Andrew Gaffney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40A637DD.70700@skylineaero.com \
--to=agaffney@skylineaero.com \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox