1 |
On Aug 29, 2005, at 10:26 PM, Brian Harring wrote: |
2 |
> |
3 |
> On Tue, Aug 30, 2005 at 01:09:49PM +1000, Finn Thain wrote: |
4 |
>>> |
5 |
>>> I was looking at it more as a place to develop some new portage |
6 |
>>> features...Gentoo/Darwin has always been lurking, this is more in |
7 |
>>> the |
8 |
>>> area of just getting offsets working. |
9 |
>> Excepting that, if you can leverage |
10 |
>> existing packages, prefixed installs are much more useful -- having a |
11 |
>> complete set of deps installed on a prefix is not much better than a |
12 |
>> stage3 chroot with your home directory bind mounted below it. |
13 |
|
14 |
Maybe so, but we can't have one without the other. First get packages |
15 |
to install in a prefix, then work up from there. The issue of |
16 |
leveraging existing packages is currently handled by |
17 |
package.provided, which we all know doesn't really serve our |
18 |
purposes, but I see no reason work couldn't be done in parallel on |
19 |
these issues...if you have an ebuild repo talking to and |
20 |
understanding a vendor repo such as apples Receipts or whatever, that |
21 |
will work wether the packages get installed in a prefix or not, |
22 |
likewise if we have packages that can be installed to an alt-prefix, |
23 |
they should work regardless of how portage is resolving the deps. |
24 |
|
25 |
> The rewrite's general core is intended to allow for alt |
26 |
> formats/repos/whatever jammed into it; that said, making seperate |
27 |
> formats play nice with each other (unless they can natively) isn't |
28 |
> something I think is incredibly easy to pull off, as mentioned above. |
29 |
|
30 |
Right, this would be a great feature, but I look at this as multi- |
31 |
level deps, which should come later IMHO. My goal for having a branch |
32 |
of some base packages is to hash out the namespace and all the other |
33 |
issues of portage managing a flat set of deps under an offset root. |
34 |
Once that is functional, making the offset repo talk to another repo, |
35 |
regardless of vendor, host, location, etc could be looked at. |
36 |
|
37 |
I know that its good to get a solid design before running off and |
38 |
writing a bunch of code, but it seems to me the portage rewrite has |
39 |
been thought out sufficiently to allow for this type of feature |
40 |
expansion in the future, without limiting what we can do right now. |
41 |
|
42 |
--Kito |
43 |
|
44 |
-- |
45 |
gentoo-osx@g.o mailing list |