From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] sys-build
Date: Sat Jan 27 08:58:01 2001 [thread overview]
Message-ID: <3A72E971.21CE995B@gottinger.de> (raw)
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.
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
Achim**
next reply other threads:[~2001-01-27 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 8:58 Achim Gottinger [this message]
2001-01-27 10:04 ` [gentoo-dev] sys-build drobbins
2001-01-27 10:36 ` Achim Gottinger
2001-01-27 11:00 ` Andreas Schweitzer
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=3A72E971.21CE995B@gottinger.de \
--to=320095285153-0001@t-online.de \
--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