1 |
Andreas Schweitzer wrote: |
2 |
|
3 |
> On Sat, Jan 27, 2001 at 06:07:37PM +0100, Achim Gottinger wrote: |
4 |
> > drobbins@g.o wrote: |
5 |
> > |
6 |
> > > On Sat, Jan 27, 2001 at 04:29:53PM +0100, Achim Gottinger wrote: |
7 |
> > > > Hi Guys, |
8 |
> > > > |
9 |
> > > > Today I build a working sys-build package that includes all the packages |
10 |
> > > > in sys-build, baselayout and portage. |
11 |
> |
12 |
> Sounds very interesting. |
13 |
> Where can I find it to try it out ? |
14 |
|
15 |
Not yet uploaded. |
16 |
|
17 |
> |
18 |
> |
19 |
> > > > This means we now have an environment to which we can chroot and build |
20 |
> > > > everithing else within. (I tested all sys-packages with success, so the |
21 |
> > > > rest should work too). |
22 |
> > > > I used exactly the same dir-layout as in the corresponding sys-* |
23 |
> > > > packages, so nothink statically linked remains |
24 |
> > > > after the corresponding packages are merged over. |
25 |
> > > > It is bigger(130MB, 28MB bzipped) than the 50MB I expectend it to be, |
26 |
> > > > maybe it can be reduced to around 100MB. :-/. |
27 |
> > > > What can we do now? |
28 |
> > > > |
29 |
> > > > 1. This build sytsem can be placed on a bootable cd together with the |
30 |
> > > > sources and the ebuild-tree. We can then |
31 |
> > > > unpack the build.tbz2 instead of the sys.tbz2 to our target partition, |
32 |
> > > > chroot there and build everything. |
33 |
> > > |
34 |
> > > OK, I'm very confused, so please explain how this works. Also, what |
35 |
> |
36 |
> me too :-) |
37 |
> |
38 |
> > > prevented us from just extracting sys.tbz2 and chrooting to /mnt/gentoo |
39 |
> > > and building everything? |
40 |
> > |
41 |
> > Ok, you can use sys.tbz2 too for that but build.tbz2 contains only the |
42 |
> > minimum required stuff, we can even |
43 |
> > place gcc and binutils in separate TARGET dependent packages, so it should be |
44 |
> > possible to make one cd that |
45 |
> > gives you the ability to build for all our intel targets. |
46 |
> |
47 |
> But /mnt/gentoo will contain the compiler etc. ? |
48 |
|
49 |
Yes you unpack build.tbz2 to /mnt/gentoo first. |
50 |
|
51 |
> And it will be overwritten ? |
52 |
|
53 |
Yes because build.tbz2 contains reduced to a minimum required and statically |
54 |
linked versions of packages . |
55 |
I used static linking because I want to be able to build the sys-build packages in |
56 |
one step without manually |
57 |
copying shared libraries from the system I build on. |
58 |
This offers the possibility to build you packages on every linux-system with a |
59 |
recent enogh kernel. |
60 |
You just have to unpack build.tbz2 to a temp dir mount the source-cd or a |
61 |
source-partition, chroot there |
62 |
and build as described below. |
63 |
|
64 |
> |
65 |
> Or at least some of the binaries in /mnt/gentoo ? |
66 |
> |
67 |
> > > And I assume that sys-build has nothing extra. For example, no star, no |
68 |
> > > iptables, etc? OK, I'm looking at /usr/portage/sys-build as I should |
69 |
> > > have done in the first place. Beautiful :) But please explain how the |
70 |
> > > build process is supposed to work (maybe by typing in example command-line |
71 |
> > > build install). |
72 |
> > |
73 |
> > Ok imagine you have a list of required packages that is sorted in order of |
74 |
> > dependencies |
75 |
> > and a filestructure on the cd that corresponds to that under /usr/portage |
76 |
> > |
77 |
> > --------------------------------------- |
78 |
> > Mkdir /mnt/gentoo/usr/portage |
79 |
> > mount /dev/cdrom /mnt/gentoo/usr/portage |
80 |
> > cp package-list /mnt/gentoo/root |
81 |
> > vi /mnt/gentoo/etc/make.conf |
82 |
> > chroot /mnt/gentoo |
83 |
> > source /etc/profile |
84 |
> > cd /usr/portage |
85 |
> > for i in 'cat /root/package-list'' |
86 |
> > do |
87 |
> > ebuild $i merge |
88 |
> > done |
89 |
> > --------------------------------------- |
90 |
> |
91 |
> A bit clearer. But again, this requires binaries in /mnt/gentoo |
92 |
> that you put there from unpacking build.tbz2 - right ? |
93 |
|
94 |
Yes |
95 |
|
96 |
> |
97 |
> |
98 |
> And there are no sources in build.tbz2 ? |
99 |
|
100 |
No |
101 |
|
102 |
> |
103 |
> Those should also be on the CDROM ? |
104 |
> Alternatively, include wget and rsync, and the sources can |
105 |
> be grabbed from the net (if somebody wants to get them from there). |
106 |
|
107 |
wget is on the boot-cd image, rsync not yes. All the required binaries and all |
108 |
kernel-network/nfs modules to |
109 |
set-up a network enviroment are on the bootcd-image. So it should not be to |
110 |
difficult to add that option too. |
111 |
|
112 |
achim~ |
113 |
|
114 |
> |
115 |
> |
116 |
> Still a newbie to gentoo - but it looks promising ! |
117 |
> |
118 |
> Cheers |
119 |
> Andreas |
120 |
> |
121 |
> -- |
122 |
> Department of Physics & Astronomy and Center for Simulational Physics |
123 |
> University of Georgia Phone ++1 (706) 542 5043 |
124 |
> Athens, GA 30602-2451 Fax ++1 (706) 542 2492 |
125 |
> USA http://dilbert.physast.uga.edu/~andy/ |
126 |
> |
127 |
> _______________________________________________ |
128 |
> gentoo-dev mailing list |
129 |
> gentoo-dev@g.o |
130 |
> http://www.gentoo.org/mailman/listinfo/gentoo-dev |