1 |
Kristian Benoit wrote: |
2 |
> On Thu, 2005-08-11 at 14:19 -0400, Alec Warner wrote: |
3 |
> |
4 |
>>Christopher Korn wrote: |
5 |
>> |
6 |
>> |
7 |
>>>>>Hi Jason and other folks, |
8 |
>>>>>I saw your last comment on |
9 |
>>>>>http://bugs.gentoo.org/show_bug.cgi?id=73350 about most the these |
10 |
>>>>>feature to be present in the next major version. That is really |
11 |
>>>>>great to read. |
12 |
>>>>> |
13 |
>>>>>On that subject, I'd like to have an idea about when we should |
14 |
>>>>>expect that next version. |
15 |
>>>>> |
16 |
>>>>>That said, I think it would be helpful to have a portage developper |
17 |
>>>>>site. Perhaps there is and I dont know... |
18 |
>>>>> |
19 |
>>>>> |
20 |
>>>> |
21 |
>>>> That would require someone writing one, so if you are |
22 |
>>>>volunteering ;) |
23 |
>>>> |
24 |
>>>> |
25 |
>>> |
26 |
>>> |
27 |
>>>Writing is not the problem. But without (proper) information it is hard |
28 |
>>>to write a documentation or something like this. |
29 |
>>> |
30 |
>>> |
31 |
>>>Chris |
32 |
>>> |
33 |
>>> |
34 |
>> |
35 |
>>I had a wiki that attempted to cover portage-2.0 api documentation as |
36 |
>>well as anything written for 2.1 but lost much of the work in a |
37 |
>>transition from windows to linux ( I screwed up the SQl backups :) ). |
38 |
>>I thought about putting something up on the devwiki but I haven't |
39 |
>>proposed anything because no one really likes a wiki for API docs. |
40 |
>> |
41 |
>>As for API docs, there are none at present; and there are no plans for |
42 |
>>any stable docs, IIRC. |
43 |
>> |
44 |
>>As for a developer website, what kinds of information are you looking for? |
45 |
> |
46 |
> |
47 |
> Like you talked about, doc would be nice, Jason has some doc, api doc... |
48 |
> here: |
49 |
> http://dev.gentoo.org/~jstubbs/ |
50 |
> but it does not look and is not official. |
51 |
> |
52 |
> I remember, when I started using Gentoo, reading that portage is a stand |
53 |
> alone tool, it is not bind into Gentoo in anyway, someone could use it |
54 |
> on redhat, debian, lfs... |
55 |
> |
56 |
> Back then I was using lfs so I thought portage could be the way to go on |
57 |
> lfs, but I realized that Gentoo fit my needs and I did'nt have to |
58 |
> compile everything by hand anymore and still have everything compiled by |
59 |
> my machines :) OH JOY !!! |
60 |
> |
61 |
> But 5 years or so later, the only official place to get portage releases |
62 |
> is still in the gentoo mirrors. There is no RSS feed or anything like |
63 |
> that. I still believe that portage has the potential to be so powerful |
64 |
> that redhat, debian, ... could be building their packages using portage, |
65 |
> managing their own tree, having night build. |
66 |
> |
67 |
> The problem is see, is that the initial portage vision (or perhaps my |
68 |
> initial vision, a vision I still have) has not been carried along with |
69 |
> it's developpement. |
70 |
"portage-ng", as it were? IMHO portage is a far cry from what is |
71 |
needed for any kind of intense platform development. I'm not going to |
72 |
harp on it's problems; everyone already knows what they are and we have |
73 |
people who are dedicated to working on it. No one has seen the code |
74 |
from portage-ng, so it was abandoned. The goals set for 2.1 and beyond |
75 |
seem lofty, and integrating portage into a non-gentoo environment is |
76 |
tricky at best, even with a nicely rewritten API. I don't see why other |
77 |
distributions would turn to our tools when theirs work perfectly fine in |
78 |
90% of cases. However, if they end up benefitting, more power to them. |
79 |
Thats why we are all here, is it not? |
80 |
|
81 |
> |
82 |
> Having an official web site, doc, ... will help getting visibility and |
83 |
> effort from the rest of the world thus we'll have better tools and |
84 |
> eventually extend portage beyond Gentoo. |
85 |
> |
86 |
> Kristian |
87 |
> |
88 |
|
89 |
-- |
90 |
gentoo-portage-dev@g.o mailing list |