1 |
On Aug 10, 2005, at 11:58 AM, Hasan Khalil wrote: |
2 |
|
3 |
|
4 |
>>>> Please note that there's probably a good deal more documentation |
5 |
>>>> work to be done, but I feel that it's probably smarter to get |
6 |
>>>> the updates published in stages rather than all at once. At the |
7 |
>>>> very least, it allows for better QA analysis of each revision. |
8 |
>>>> Kito: I apologize in advance if I butchered the description of |
9 |
>>>> the progressive profile. Please feel free to slap me with a very |
10 |
>>>> large, very freshly-dead herring, and submit corrections as |
11 |
>>>> necessary. |
12 |
>>>> |
13 |
>> |
14 |
>> Attached is a rough description of the progressive profile. |
15 |
>> |
16 |
> |
17 |
> Okay, looks like you wrote a good deal there, and I like it. I had |
18 |
> originally planned on having at least one separate section |
19 |
> (possibly one per profile) on just what the different profiles were |
20 |
> all about, but I felt it would be better to implement the changes |
21 |
> in phases. That being said, I think it's wise to hold off on it and |
22 |
> just provide a short description for now. Is the short description |
23 |
> on there unacceptable, even as it's temporary? |
24 |
> |
25 |
> Furthermore, I'm not sure that the installation/usage guide, at |
26 |
> least in its current form, would be a good place for this |
27 |
> information. What I'd like to see is for the guide to be expanded |
28 |
> into a proper book with separate pages on each important detail |
29 |
> (for now, I see at least 4 pages: Project/Installation Notes, |
30 |
> Installation Guide, Usage Guide, Troubleshooting/Known Issues/ |
31 |
> Whatever). Before doing anything of the sort, I'll consult this |
32 |
> mailing list, of course. :) |
33 |
> |
34 |
|
35 |
Hmmm, not sure I agree... Since the profile is something that should |
36 |
be decided during bootstrap.... Since this is what we have, why not |
37 |
put it on there now? Sure when this page gets obscenely verbose, we |
38 |
can start splitting it up, but I think it would be fine to have |
39 |
descriptions there for now... |
40 |
|
41 |
> |
42 |
>> I would suggest getting rid of the section telling users to |
43 |
>> keyword ebuilds directly, and instead point them to the /etc/ |
44 |
>> portage/* files. As more of the base-system packages get the ~ppc- |
45 |
>> macos keyword for the progressive profile, I suspect users will be |
46 |
>> confused when they see an ebuild with the ~ppc-macos keyword but |
47 |
>> still being unable to emerge as a result of it being masked for |
48 |
>> file collisions on the standard profiles. |
49 |
>> |
50 |
> |
51 |
> I completely agree. I'd really like to ditch the whole section in |
52 |
> exchange for a paragraph and a link to some already existing |
53 |
> resource, if some such pertinent resource already exists (maybe |
54 |
> just refer them to `man portage`?). I don't plan on changing it |
55 |
> with this release, though; I'd really like to get this through the |
56 |
> door as quickly as possible since there are some important |
57 |
> alterations there. |
58 |
> |
59 |
|
60 |
Why the big hurry? seems if we are going through the trouble now, |
61 |
might as well kill all the birds we can with this rock ;) |
62 |
|
63 |
> |
64 |
>> We should probably also mention the fact that the installer has |
65 |
>> the bug of portage not knowing its installed, so probably just |
66 |
>> tell them to `FEATURES="-collision-protect" sudo emerge --nodeps |
67 |
>> portage` to avoid the endless dup bugs being filed and the same |
68 |
>> question being asked in #-osx. |
69 |
>> |
70 |
> |
71 |
> Absolutely. I'll add this Real Soon Now(tm). |
72 |
> |
73 |
> Thanks all for your feedback. Any other issues? |
74 |
> |
75 |
> -- |
76 |
> |
77 |
> Hasan Khalil |
78 |
> eBuild and Porting Co-Lead |
79 |
> Gentoo for Mac OS X |
80 |
> |
81 |
> |
82 |
|
83 |
-- |
84 |
gentoo-osx@g.o mailing list |