Re: [gentoo-dev] sys-build

[320095285153-0001@t-online.de (Achim Gottinger)]

drobbins@gentoo.org wrote:

> On Sat, Jan 27, 2001 at 04:29:53PM +0100, Achim Gottinger wrote:
> > Hi Guys,
> >
> > Today I build a working sys-build package that includes all the packages
> > in sys-build, baselayout and portage.
> > This means we now have an environment to which we can chroot and build
> > everithing else within. (I tested all sys-packages with success, so the
> > rest should work too).
> > I used exactly the same dir-layout as in the corresponding sys-*
> > packages, so nothink statically linked remains
> > after the corresponding packages are merged over.
> > It is bigger(130MB, 28MB bzipped) than the 50MB I expectend it to be,
> > maybe it can be reduced to around 100MB. :-/.
> > What can we do now?
> >
> > 1. This build sytsem can be placed on a bootable cd together with the
> > sources and the ebuild-tree. We can then
> > unpack the build.tbz2 instead of the sys.tbz2 to our target partition,
> > chroot there and build everything.
>
> OK, I'm very confused, so please explain how this works.  Also, what
> prevented us from just extracting sys.tbz2 and chrooting to /mnt/gentoo
> and building everything?

Ok, you can use sys.tbz2 too for that but build.tbz2 contains only the
minimum required stuff, we can even
place gcc and binutils in separate TARGET dependent packages, so it should be
possible to make one cd that
gives you the ability to build for all our intel targets.

>
>
> When you say building everything, do you mean *re*building the base system
> as well?  Does this system use a separate build partition and target
> partition, or just a single root partition mounted at /mnt/gentoo?

Well there is no base-system that needs to be rebuild. Instead the
corresponding non statically linked packages
get build and merged over or can be unmerged if not required after the build.

All is done on one partition, no fiddeling around with crosscompilers is
required.

>
>
> And I assume that sys-build has nothing extra.  For example, no star, no
> iptables, etc?  OK, I'm looking at /usr/portage/sys-build as I should
> have done in the first place.  Beautiful :)  But please explain how the
> build process is supposed to work (maybe by typing in example command-line
> build install).

Ok imagine you have a list of required packages that is sorted in order of
dependencies
and a filestructure on the cd that corresponds to that under /usr/portage

---------------------------------------
mkdir /mnt/gentoo/usr/portage
mount /dev/cdrom /mnt/gentoo/usr/portage
cp package-list /mnt/gentoo/root
vi /mnt/gentoo/etc/make.conf
chroot /mnt/gentoo
source /etc/profile
cd /usr/portage
for i in 'cat /root/package-list''
do
    ebuild $i merge
done
---------------------------------------


>
>
> > 2. We can use this as a starting point for ports to other platforms. It
> > should be possible to build the sys-build stuff
> > if we have ports of spython and portage and gcc-2.95.2 on the
> > base-system.
> >
> > 3. There is no more need for the other sys-categories now so these
> > packages can be moved to the other categories now. So we are one step
> > closer to a minimum runtime system now.
> >
> > Feedback please
>
> Is sys-build becoming our "official" install method?

Hmm, no but I think we can offer source-cd this as an alternative to the
package-cd.
We can put spython and the pkgmerge part of portage on our bootcd-img on the
package-cd and provide
several profile lists and later a package-management-gui.

> Or will you continue
> to make a sys.tbz2?  Or just a build.tbz2 and then all other packages will
> be in their own individual package tarballs and we'll add the new system
> profile (server,desktop,etc) capability to portage to help decide which
> .tbz2's to install.  This feature isn't ready for -rc4 but it can be for
> -final.

Maybe we make an rc5 for that.

>
>
> Lots of questions this time,

Hope all answerd.

Achim~~

>
>
> Best Regards,
>
> --
> Daniel Robbins                                  <drobbins@gentoo.org>
> President/CEO                                   http://www.gentoo.org
> Gentoo Technologies, Inc.
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev