1 |
drobbins@g.o wrote: |
2 |
|
3 |
> On Sat, Jan 27, 2001 at 04:29:53PM +0100, Achim Gottinger wrote: |
4 |
> > Hi Guys, |
5 |
> > |
6 |
> > Today I build a working sys-build package that includes all the packages |
7 |
> > in sys-build, baselayout and portage. |
8 |
> > This means we now have an environment to which we can chroot and build |
9 |
> > everithing else within. (I tested all sys-packages with success, so the |
10 |
> > rest should work too). |
11 |
> > I used exactly the same dir-layout as in the corresponding sys-* |
12 |
> > packages, so nothink statically linked remains |
13 |
> > after the corresponding packages are merged over. |
14 |
> > It is bigger(130MB, 28MB bzipped) than the 50MB I expectend it to be, |
15 |
> > maybe it can be reduced to around 100MB. :-/. |
16 |
> > What can we do now? |
17 |
> > |
18 |
> > 1. This build sytsem can be placed on a bootable cd together with the |
19 |
> > sources and the ebuild-tree. We can then |
20 |
> > unpack the build.tbz2 instead of the sys.tbz2 to our target partition, |
21 |
> > chroot there and build everything. |
22 |
> |
23 |
> OK, I'm very confused, so please explain how this works. Also, what |
24 |
> prevented us from just extracting sys.tbz2 and chrooting to /mnt/gentoo |
25 |
> and building everything? |
26 |
|
27 |
Ok, you can use sys.tbz2 too for that but build.tbz2 contains only the |
28 |
minimum required stuff, we can even |
29 |
place gcc and binutils in separate TARGET dependent packages, so it should be |
30 |
possible to make one cd that |
31 |
gives you the ability to build for all our intel targets. |
32 |
|
33 |
> |
34 |
> |
35 |
> When you say building everything, do you mean *re*building the base system |
36 |
> as well? Does this system use a separate build partition and target |
37 |
> partition, or just a single root partition mounted at /mnt/gentoo? |
38 |
|
39 |
Well there is no base-system that needs to be rebuild. Instead the |
40 |
corresponding non statically linked packages |
41 |
get build and merged over or can be unmerged if not required after the build. |
42 |
|
43 |
All is done on one partition, no fiddeling around with crosscompilers is |
44 |
required. |
45 |
|
46 |
> |
47 |
> |
48 |
> And I assume that sys-build has nothing extra. For example, no star, no |
49 |
> iptables, etc? OK, I'm looking at /usr/portage/sys-build as I should |
50 |
> have done in the first place. Beautiful :) But please explain how the |
51 |
> build process is supposed to work (maybe by typing in example command-line |
52 |
> build install). |
53 |
|
54 |
Ok imagine you have a list of required packages that is sorted in order of |
55 |
dependencies |
56 |
and a filestructure on the cd that corresponds to that under /usr/portage |
57 |
|
58 |
--------------------------------------- |
59 |
mkdir /mnt/gentoo/usr/portage |
60 |
mount /dev/cdrom /mnt/gentoo/usr/portage |
61 |
cp package-list /mnt/gentoo/root |
62 |
vi /mnt/gentoo/etc/make.conf |
63 |
chroot /mnt/gentoo |
64 |
source /etc/profile |
65 |
cd /usr/portage |
66 |
for i in 'cat /root/package-list'' |
67 |
do |
68 |
ebuild $i merge |
69 |
done |
70 |
--------------------------------------- |
71 |
|
72 |
|
73 |
> |
74 |
> |
75 |
> > 2. We can use this as a starting point for ports to other platforms. It |
76 |
> > should be possible to build the sys-build stuff |
77 |
> > if we have ports of spython and portage and gcc-2.95.2 on the |
78 |
> > base-system. |
79 |
> > |
80 |
> > 3. There is no more need for the other sys-categories now so these |
81 |
> > packages can be moved to the other categories now. So we are one step |
82 |
> > closer to a minimum runtime system now. |
83 |
> > |
84 |
> > Feedback please |
85 |
> |
86 |
> Is sys-build becoming our "official" install method? |
87 |
|
88 |
Hmm, no but I think we can offer source-cd this as an alternative to the |
89 |
package-cd. |
90 |
We can put spython and the pkgmerge part of portage on our bootcd-img on the |
91 |
package-cd and provide |
92 |
several profile lists and later a package-management-gui. |
93 |
|
94 |
> Or will you continue |
95 |
> to make a sys.tbz2? Or just a build.tbz2 and then all other packages will |
96 |
> be in their own individual package tarballs and we'll add the new system |
97 |
> profile (server,desktop,etc) capability to portage to help decide which |
98 |
> .tbz2's to install. This feature isn't ready for -rc4 but it can be for |
99 |
> -final. |
100 |
|
101 |
Maybe we make an rc5 for that. |
102 |
|
103 |
> |
104 |
> |
105 |
> Lots of questions this time, |
106 |
|
107 |
Hope all answerd. |
108 |
|
109 |
Achim~~ |
110 |
|
111 |
> |
112 |
> |
113 |
> Best Regards, |
114 |
> |
115 |
> -- |
116 |
> Daniel Robbins <drobbins@g.o> |
117 |
> President/CEO http://www.gentoo.org |
118 |
> Gentoo Technologies, Inc. |
119 |
> |
120 |
> _______________________________________________ |
121 |
> gentoo-dev mailing list |
122 |
> gentoo-dev@g.o |
123 |
> http://www.gentoo.org/mailman/listinfo/gentoo-dev |