1 |
On Aug 10, 2005, at 10:50, Kito wrote: |
2 |
|
3 |
> On Aug 10, 2005, at 12:42 AM, Grobian wrote: |
4 |
> |
5 |
> |
6 |
>> Two small things that I don't know for sure: |
7 |
>> |
8 |
>> | Warning: Using any shell besides bash is currenly unsupported |
9 |
>> and most |
10 |
>> | likely won't work. You should change your default shell in |
11 |
>> Terminal by |
12 |
>> | clicking on Terminal->Preferences (in the menu bar), chosing the |
13 |
>> | "Execute this command" option, and entering /bin/bash. |
14 |
>> |
15 |
>> How likely is this? Of course I ignored this warning when |
16 |
>> installing my Gentoo, because I feel hopelessly lost in bash. On |
17 |
>> the one hand, is it known what causes trouble? and on the other |
18 |
>> hand, considering the default shell is bash from 10.3 (at least |
19 |
>> 10.4) also for the root account, and everything is done using |
20 |
>> "sudo su", how likely is it the user will use a different shell |
21 |
>> for the root user than the system provided one? On top of this, |
22 |
>> whenever the whole emerge system is getting into action a bash |
23 |
>> shell is forked from python I think, so what relevance is the |
24 |
>> parent shell to that? |
25 |
>> |
26 |
> |
27 |
> Yeah, I've always used zsh myself, with no problems to speak of. |
28 |
|
29 |
The note has been deleted in the latest revision. Thanks Kito and |
30 |
Fabian for pointing this out. |
31 |
|
32 |
>>> Please note that there's probably a good deal more documentation |
33 |
>>> work to be done, but I feel that it's probably smarter to get the |
34 |
>>> updates published in stages rather than all at once. At the very |
35 |
>>> least, it allows for better QA analysis of each revision. |
36 |
>>> Kito: I apologize in advance if I butchered the description of |
37 |
>>> the progressive profile. Please feel free to slap me with a very |
38 |
>>> large, very freshly-dead herring, and submit corrections as |
39 |
>>> necessary. |
40 |
> |
41 |
> Attached is a rough description of the progressive profile. |
42 |
|
43 |
Okay, looks like you wrote a good deal there, and I like it. I had |
44 |
originally planned on having at least one separate section (possibly |
45 |
one per profile) on just what the different profiles were all about, |
46 |
but I felt it would be better to implement the changes in phases. |
47 |
That being said, I think it's wise to hold off on it and just provide |
48 |
a short description for now. Is the short description on there |
49 |
unacceptable, even as it's temporary? |
50 |
|
51 |
Furthermore, I'm not sure that the installation/usage guide, at least |
52 |
in its current form, would be a good place for this information. What |
53 |
I'd like to see is for the guide to be expanded into a proper book |
54 |
with separate pages on each important detail (for now, I see at least |
55 |
4 pages: Project/Installation Notes, Installation Guide, Usage Guide, |
56 |
Troubleshooting/Known Issues/Whatever). Before doing anything of the |
57 |
sort, I'll consult this mailing list, of course. :) |
58 |
|
59 |
> I would suggest getting rid of the section telling users to keyword |
60 |
> ebuilds directly, and instead point them to the /etc/portage/* |
61 |
> files. As more of the base-system packages get the ~ppc-macos |
62 |
> keyword for the progressive profile, I suspect users will be |
63 |
> confused when they see an ebuild with the ~ppc-macos keyword but |
64 |
> still being unable to emerge as a result of it being masked for |
65 |
> file collisions on the standard profiles. |
66 |
|
67 |
I completely agree. I'd really like to ditch the whole section in |
68 |
exchange for a paragraph and a link to some already existing |
69 |
resource, if some such pertinent resource already exists (maybe just |
70 |
refer them to `man portage`?). I don't plan on changing it with this |
71 |
release, though; I'd really like to get this through the door as |
72 |
quickly as possible since there are some important alterations there. |
73 |
|
74 |
> We should probably also mention the fact that the installer has the |
75 |
> bug of portage not knowing its installed, so probably just tell |
76 |
> them to `FEATURES="-collision-protect" sudo emerge --nodeps |
77 |
> portage` to avoid the endless dup bugs being filed and the same |
78 |
> question being asked in #-osx. |
79 |
|
80 |
Absolutely. I'll add this Real Soon Now(tm). |
81 |
|
82 |
Thanks all for your feedback. Any other issues? |
83 |
|
84 |
-- |
85 |
|
86 |
Hasan Khalil |
87 |
eBuild and Porting Co-Lead |
88 |
Gentoo for Mac OS X |