From: Andreas Schweitzer <andy@physast.uga.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] sys-build
Date: Sat Jan 27 11:00:02 2001 [thread overview]
Message-ID: <20010127130035.A19292@bender.physast.uga.edu> (raw)
In-Reply-To: <3A730059.6C5E0FBC@gottinger.de>; from Achim Gottinger on Sat, Jan 27, 2001 at 06:07:37PM +0100
On Sat, Jan 27, 2001 at 06:07:37PM +0100, Achim Gottinger wrote:
> 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.
Sounds very interesting.
Where can I find it to try it out ?
> > > 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
me too :-)
> > 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.
But /mnt/gentoo will contain the compiler etc. ?
And it will be overwritten ?
Or at least some of the binaries in /mnt/gentoo ?
> > 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
> ---------------------------------------
A bit clearer. But again, this requires binaries in /mnt/gentoo
that you put there from unpacking build.tbz2 - right ?
And there are no sources in build.tbz2 ?
Those should also be on the CDROM ?
Alternatively, include wget and rsync, and the sources can
be grabbed from the net (if somebody wants to get them from there).
Still a newbie to gentoo - but it looks promising !
Cheers
Andreas
--
Department of Physics & Astronomy and Center for Simulational Physics
University of Georgia Phone ++1 (706) 542 5043
Athens, GA 30602-2451 Fax ++1 (706) 542 2492
USA http://dilbert.physast.uga.edu/~andy/
next prev parent reply other threads:[~2001-01-27 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 8:58 [gentoo-dev] sys-build Achim Gottinger
2001-01-27 10:04 ` drobbins
2001-01-27 10:36 ` Achim Gottinger
2001-01-27 11:00 ` Andreas Schweitzer [this message]
2001-01-27 11:16 ` Achim Gottinger
2001-01-27 13:04 ` Andreas Schweitzer
2001-01-27 13:57 ` Achim Gottinger
2001-01-27 11:13 ` drobbins
2001-01-27 11:26 ` Achim Gottinger
2001-01-27 11:34 ` drobbins
2001-01-27 13:00 ` Andreas Schweitzer
2001-01-27 14:04 ` Achim Gottinger
2001-01-27 14:27 ` Achim Gottinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010127130035.A19292@bender.physast.uga.edu \
--to=andy@physast.uga.edu \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox