| 1 |
On Sat, Jan 27, 2001 at 04:29:53PM +0100, Achim Gottinger wrote: |
| 2 |
> Hi Guys, |
| 3 |
> |
| 4 |
> Today I build a working sys-build package that includes all the packages |
| 5 |
> in sys-build, baselayout and portage. |
| 6 |
> This means we now have an environment to which we can chroot and build |
| 7 |
> everithing else within. (I tested all sys-packages with success, so the |
| 8 |
> rest should work too). |
| 9 |
> I used exactly the same dir-layout as in the corresponding sys-* |
| 10 |
> packages, so nothink statically linked remains |
| 11 |
> after the corresponding packages are merged over. |
| 12 |
> It is bigger(130MB, 28MB bzipped) than the 50MB I expectend it to be, |
| 13 |
> maybe it can be reduced to around 100MB. :-/. |
| 14 |
> What can we do now? |
| 15 |
> |
| 16 |
> 1. This build sytsem can be placed on a bootable cd together with the |
| 17 |
> sources and the ebuild-tree. We can then |
| 18 |
> unpack the build.tbz2 instead of the sys.tbz2 to our target partition, |
| 19 |
> chroot there and build everything. |
| 20 |
|
| 21 |
OK, I'm very confused, so please explain how this works. Also, what |
| 22 |
prevented us from just extracting sys.tbz2 and chrooting to /mnt/gentoo |
| 23 |
and building everything? |
| 24 |
|
| 25 |
When you say building everything, do you mean *re*building the base system |
| 26 |
as well? Does this system use a separate build partition and target |
| 27 |
partition, or just a single root partition mounted at /mnt/gentoo? |
| 28 |
|
| 29 |
And I assume that sys-build has nothing extra. For example, no star, no |
| 30 |
iptables, etc? OK, I'm looking at /usr/portage/sys-build as I should |
| 31 |
have done in the first place. Beautiful :) But please explain how the |
| 32 |
build process is supposed to work (maybe by typing in example command-line |
| 33 |
build install). |
| 34 |
|
| 35 |
> 2. We can use this as a starting point for ports to other platforms. It |
| 36 |
> should be possible to build the sys-build stuff |
| 37 |
> if we have ports of spython and portage and gcc-2.95.2 on the |
| 38 |
> base-system. |
| 39 |
> |
| 40 |
> 3. There is no more need for the other sys-categories now so these |
| 41 |
> packages can be moved to the other categories now. So we are one step |
| 42 |
> closer to a minimum runtime system now. |
| 43 |
> |
| 44 |
> Feedback please |
| 45 |
|
| 46 |
Is sys-build becoming our "official" install method? Or will you continue |
| 47 |
to make a sys.tbz2? Or just a build.tbz2 and then all other packages will |
| 48 |
be in their own individual package tarballs and we'll add the new system |
| 49 |
profile (server,desktop,etc) capability to portage to help decide which |
| 50 |
.tbz2's to install. This feature isn't ready for -rc4 but it can be for |
| 51 |
-final. |
| 52 |
|
| 53 |
Lots of questions this time, |
| 54 |
|
| 55 |
Best Regards, |
| 56 |
|
| 57 |
|
| 58 |
-- |
| 59 |
Daniel Robbins <drobbins@g.o> |
| 60 |
President/CEO http://www.gentoo.org |
| 61 |
Gentoo Technologies, Inc. |
Archives