1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Saturday 15 May 2004 15:50, Andrew Gaffney wrote: |
5 |
> Jason Stubbs wrote: |
6 |
> > On Saturday 15 May 2004 13:12, Andrew Gaffney wrote: |
7 |
> >>>You've already done a complete rewrite of the dependency resolver? |
8 |
> > |
9 |
> > Yes and no. I started from scratch but used almost exactly the same |
10 |
> > logic. I guess you could almost call it refactoring. Have a look at: |
11 |
> > http://www.gentoo.org/cgi-bin/viewcvs.cgi/portage-mod/portageapi/?root=ge |
12 |
> >ntoo-src |
13 |
> > |
14 |
> > Of interest to you, will probably be dep.py. Even if you do not |
15 |
> > understand python, the logic should be fairly clear (I hope!). The only |
16 |
> > real change from the above logic is that installed packages (including |
17 |
> > their original USE flags and *DEPENDs) are also taken into account. |
18 |
> |
19 |
> I'll have to take a look at it. If anyone wants to take a look at my code |
20 |
> (and maybe give me a few suggestions), the (almost) latest working version |
21 |
> can be accessed at <http://locutus.homeip.net/dev/portage.pl>. It currently |
22 |
> operates the same way 'emerge -ep' would. It doesn't generate the exact |
23 |
> same packages to install as Portage, but it is pretty damn close. |
24 |
|
25 |
May I ask what you are writing this for? Once the API I'm working on is |
26 |
completed, tested and integrated (<2 months?) I'll start working on wrappers |
27 |
for other languages. Is that the sort of thing you are after? |
28 |
|
29 |
Regards, |
30 |
Jason Stubbs |
31 |
-----BEGIN PGP SIGNATURE----- |
32 |
Version: GnuPG v1.2.4 (GNU/Linux) |
33 |
|
34 |
iQCVAwUBQKXBfFoikN4/5jfsAQKMLwP8DS8XempV3Sz8AN9+q0tT0HqjFC76BxHN |
35 |
7xRcAwu0y3KkM1Bf1f7Ezs/chzzqJtNcDcWUVECtiMbMa3F2MWPyB7cn034eCxDt |
36 |
02H2WruxweT6NHFdSCRhEqbBmrmvBW9Hvfdzii9JMzruEA6C/V8b0peHv0B3Fauy |
37 |
nQTzlecx9Mg= |
38 |
=e/X+ |
39 |
-----END PGP SIGNATURE----- |
40 |
|
41 |
-- |
42 |
gentoo-portage-dev@g.o mailing list |