| 1 |
On 9/19/06, Richard Fish <bigfish@××××××××××.org> wrote: |
| 2 |
> On 9/19/06, Alon Keren <alon.keren@×××××.com> wrote: |
| 3 |
> > My aim is to have the ability to regularly build and maintain |
| 4 |
> > completely customized Linux systems. |
| 5 |
> |
| 6 |
> This should be possible by using your own local portage tree (probably |
| 7 |
> based initially on Gentoo's tree) that you update somewhat manually |
| 8 |
> with ebuilds and eclasses as you want. Combined with pre-built binary |
| 9 |
> packages, and a 'golden' portage configuration and world file, it |
| 10 |
> should be relatively simple & quick to stage a new system. |
| 11 |
> |
| 12 |
.... |
| 13 |
> |
| 14 |
> This _is_ going to require a solid understanding of how Gentoo/Portage |
| 15 |
> works, but not necessarily how to write ebuilds/eclasses. You need to |
| 16 |
> understand what we mean by "portage tree", "world file", "use flags", |
| 17 |
> "profile", "binary packages", etc. The best way to acquire this |
| 18 |
> knowledge is to install and use Gentoo, daily, for something |
| 19 |
> significant (like your desktop!). |
| 20 |
> |
| 21 |
Yes, I realize that deep understanding of Portage would obviously be |
| 22 |
required, as will writing ebuilds (and copying some of Gentoo's). |
| 23 |
|
| 24 |
> > The ROOT variable is probably a major part of the solution, but is it |
| 25 |
> > enough? I've also found '/usr/portage/scripts/bootstrap.sh', which |
| 26 |
> > seems suspiciously relevant, but comes with little external |
| 27 |
> > documentation. |
| 28 |
> |
| 29 |
> bootstrap.sh _is_ for only rebuilding the toolchain. Probably not |
| 30 |
> what you want at all.... |
| 31 |
> |
| 32 |
It's actually what I DO want. As I've previously explained, it would |
| 33 |
give me the control I need over the system. |
| 34 |
|
| 35 |
|
| 36 |
> If Gentoo's minimal installation CD and a stage1 install doesn't work |
| 37 |
> for you, you can build your own release media with catalyst (no, it |
| 38 |
> isn't just for rebuilding the toolchain). |
| 39 |
Release media would be good, but I'd like to know how more about how |
| 40 |
Catalyst produces the toolchain. |
| 41 |
|
| 42 |
> The ROOT variable is used to install packages into a different (fex |
| 43 |
> chroot) directory. It is usually used for things like |
| 44 |
> cross-compilation environments where one wants to build binary |
| 45 |
> packages for another system, although not always. |
| 46 |
> |
| 47 |
Cross-compilation is something I would like to be able to do. |
| 48 |
|
| 49 |
>From what I've gathered so far, it looks llike it should be possible |
| 50 |
to build a complete customized toolchain with Portage, even if it'd |
| 51 |
require some tweaking; at the center of it being the ROOT env. |
| 52 |
variable and 'bootloader.sh'. Still, I wish I could get input from |
| 53 |
someone who's actually done such a thing. |
| 54 |
|
| 55 |
|
| 56 |
Alon |
| 57 |
|
| 58 |
|
| 59 |
PS. |
| 60 |
|
| 61 |
Please CC me your replies as I'm not subscribed to messages from this list |
| 62 |
-- |
| 63 |
gentoo-user@g.o mailing list |
Archives