| 1 |
On Fri, 2007-05-25 at 17:24 +0200, Fabian Groffen wrote: |
| 2 |
> On 25-05-2007 17:17:11 +0200, Michael Haubenwallner wrote: |
| 3 |
> <snip> |
| 4 |
> > Well, 'prefix-launcher' installs a script 'eprefix-bootstrap' as a |
| 5 |
> > separate package, which downloads current 'bootstrap-prefix.sh', but |
| 6 |
> > uses it only for setting up the tree and the configurations. |
| 7 |
> > There is no need to build bootstrap-packages again, as those are |
| 8 |
> > provided by prefix-launcher. |
| 9 |
> |
| 10 |
> Ohw. Then it's time to merge some things together maybe. |
| 11 |
|
| 12 |
Ehm, maybe. Having three different things is somewhat useful too, I |
| 13 |
suggest better just moving things from one script to another. |
| 14 |
|
| 15 |
<braindump> |
| 16 |
eprefix-bootstrap is (designed to be) useable standalone, without |
| 17 |
prefix-launcher. So it could be emerged as separate package. |
| 18 |
It just uses tools (wget,gcc,...,prefix-portage) to bootstrap another |
| 19 |
eprefix. |
| 20 |
|
| 21 |
prefix-launcher just provides these tools for environments lacking them. |
| 22 |
|
| 23 |
But also a working eprefix provides them. |
| 24 |
|
| 25 |
And once prefix-branch is merged to mainline, this very same tools are |
| 26 |
available on a main gentoo box without additional efford, so there is no |
| 27 |
need for prefix-launcher any more, but still eprefix-bootstrap. |
| 28 |
|
| 29 |
And for other linux-distros, why not have prefix-portage and |
| 30 |
eprefix-bootstrap available as rpm, deb, pkg, depot, whatever... |
| 31 |
|
| 32 |
Now having either prefix-launcher, a working eprefix, main gentoo or |
| 33 |
some other system with prefix-portage, I want to bootstrap a fresh |
| 34 |
eprefix there. |
| 35 |
|
| 36 |
So eprefix-bootstrap (no need to be very up-to-date) downloads the |
| 37 |
current prefix-bootstrap.sh, knowing best how to set up for the current |
| 38 |
snapshot's profiles. |
| 39 |
|
| 40 |
Here's the thing I suggest to be moved: |
| 41 |
|
| 42 |
The real bootstrap-action currently is done within eprefix-bootstrap, |
| 43 |
mainly because I do not have commit-access to bootstrap-prefix.sh (yet). |
| 44 |
|
| 45 |
So I would keep downloading and calling bootstrap-prefix.sh within |
| 46 |
eprefix-bootstrap, but move the individual emerge-calls for a working |
| 47 |
'system' into bootstrap-prefix.sh, and leave building bootstrap packages |
| 48 |
to prefix-launcher. |
| 49 |
</braindump> |
| 50 |
|
| 51 |
/haubi/ |
| 52 |
|
| 53 |
-- |
| 54 |
gentoo-alt@g.o mailing list |
Archives