| 1 |
On 07-09-2007 20:23:45 +0200, Elias Pipping wrote: |
| 2 |
> ( no, that's not valid sed syntax but i think it looks better than |
| 3 |
> 'replace ... with ...' ) |
| 4 |
> |
| 5 |
> |
| 6 |
> > [..] such that source code can be compiled into workin executables. |
| 7 |
> s/workin/working |
| 8 |
|
| 9 |
Already tackled that one |
| 10 |
|
| 11 |
> > The first step is to chose a path to install into. |
| 12 |
> s/chose/choose |
| 13 |
> |
| 14 |
> > stored in the variable $EPREFIX. |
| 15 |
> s/$EPREFIX/EPREFIX |
| 16 |
|
| 17 |
Will try to make it consistent all over the place |
| 18 |
|
| 19 |
> > [..] in your soon to be prefix to your PATH environment. |
| 20 |
> s/./: |
| 21 |
|
| 22 |
Taste/style |
| 23 |
|
| 24 |
> > [..] You can skip bootstrapping python if you already have a working Python 2.4 in your path. |
| 25 |
> s/2.4/2.4 or better |
| 26 |
> |
| 27 |
> > [..] Afterwards it will try to setup some sane defaults. |
| 28 |
> s/setup/set up |
| 29 |
> |
| 30 |
> > Next, we emerge the bash shell and its dependency ncurses. |
| 31 |
> s/the bash shell/the bash |
| 32 |
|
| 33 |
The bash? |
| 34 |
|
| 35 |
Either bash, or the bash shell, imo. |
| 36 |
|
| 37 |
Thanks! |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
Fabian Groffen |
| 42 |
Gentoo on a different level |
| 43 |
-- |
| 44 |
gentoo-alt@g.o mailing list |
Archives