1 |
the real problem stands in the keyword.... the amd64 would downgrade a lot |
2 |
of stuff.... before doing it it's better to identify the normal programs, |
3 |
like kde, gnome, and similar and let them be for the moment as ~amd64.... |
4 |
but at least stuff like, gcc, glibc, baselayout, kernel and some other base |
5 |
stuff should stay on the amd64 branch.... you won't be able to downgrade |
6 |
glibc so that one for the moment would stay on the unstable branch.... but |
7 |
if you don't feel in the mood to downgrade cause the ~amd64 being to amd64, |
8 |
then just update the profile and you should see something like 100 |
9 |
packages.... |
10 |
also adding --as-needed as LDFLAGS should help you save some time in |
11 |
recompiling stuff.... |
12 |
the 2gb of ccache would help, but not a lot.... 400+ packages would mean |
13 |
about 3-4 days on a amd64 2ghz single core, so prepare for a looong time of |
14 |
compile time.... also the 5 blockers are not good and should be fixed in |
15 |
some way before proceeding to the recompile.... |
16 |
if you decide to modify the use flags when changing profile it's the best |
17 |
time.... |
18 |
so my advice is the following: |
19 |
1. take some time to look at the use flags (emerge ufed and see a |
20 |
description of them and also add/remove them from the ufed gui in make.conf) |
21 |
2. add LDFLAGS="--as-needed" into make.conf |
22 |
3. take some time to see what packages are needed on ~amd64 (normally kde, |
23 |
gnome, and other normal use packages like firefox, ktorrent or similar or |
24 |
even xorg are good also on ~amd64 and don't need a downgrade), but others as |
25 |
gcc, baselayout, libstdc++, dhcpclient, dhcpcd, network related packages and |
26 |
kernel modules are normally best on amd64. i'm not saying that using them on |
27 |
~amd64 won't work, but on this branch you might experience various problems. |
28 |
after deciding what you want to mantain as ~amd64 you add them to |
29 |
package.keywords in /et/portage/ with ~amd64 flag and then remove the flag |
30 |
in make.conf. after that retry the update and see that the number of |
31 |
packages has decreased dramatically. take another look at the downgraded |
32 |
stuff and after being sure you could start the update of your system. |
33 |
this step is a little boring, but after some time spent on configuration, |
34 |
unmask and mask you'll find yourself with a system with the following |
35 |
characteristics: |
36 |
- base system = stable |
37 |
- cutting edge apps, which sometimes could bring out some problems, but that |
38 |
wouldn't be caused by system packages faults. |
39 |
|
40 |
if you want to see some more stuff i reccomend the following overlays: |
41 |
- sunrise: has a lot of extra interesting stuff of various kind, from |
42 |
developer stuff to user apps as miro, the free web tv player that challenges |
43 |
joost. |
44 |
- sabayon: has some interesting things like the kde4 style kicker for |
45 |
3.5.8branch |
46 |
- flameeyes-overlay: has some memory improved stuff like patched codecs and |
47 |
the oxy-cursors that are really great. from this overlay be sure not to |
48 |
compile the xine-lib because it's not meant to work with versions of amarok |
49 |
before the 2.0 and since it has some issues caused by the developing process |
50 |
(this xine-lib is meant for integration with kde4 and phonon). i recommend |
51 |
the other codecs like giflib and theora since they have a patch for shared |
52 |
memory improvements. i also reccomend the ffmpeg with hardcoded-tables flag |
53 |
from this overlay. |
54 |
- berkano: has some media related packages like x264-svn, new k3b and some |
55 |
other media packages |
56 |
- x11: if you want svn versions of xorg and its components add this overlay. |
57 |
i've seen some great improvements with the new xf86-video-ati after it has |
58 |
ggod support for x200m and rs690 and the new mesa and glitz from svn have |
59 |
some font antialiasing stuff that is really interesting. |
60 |
to add them emerge layman and use it to update and mantain the new |
61 |
repositories. on gentoo wiki there are wikis on how to install and use |
62 |
layman. |
63 |
if you need some help with the packages or use flags feel free to ask. i'll |
64 |
try explaining what are my experiences with them. |
65 |
remember to run revdep-rebuild after updating since it's very likely to have |
66 |
broken linkage after an update of 400 packages. |
67 |
|
68 |
ps. consider the profile update as a gentoo full update. if you think about |
69 |
distro that use versioning then it's similar to updating to ubuntu 7 from |
70 |
ubuntu 6. so it's normal to have a lot of packages pushed in considering use |
71 |
flags changes and keywords ones. |
72 |
|
73 |
|
74 |
|
75 |
2008/1/29, agtdino <agtdino@××××××××.es>: |
76 |
> |
77 |
> Hi, |
78 |
> |
79 |
> |
80 |
> # eselect profile list |
81 |
> Available profile symlink targets: |
82 |
> [1] default-linux/amd64/2006.1 * |
83 |
> [2] default-linux/amd64/2006.1/desktop |
84 |
> [3] default-linux/amd64/2006.0/no-symlinks |
85 |
> [4] default-linux/amd64/2006.1/no-multilib |
86 |
> [5] default-linux/amd64/2007.0 |
87 |
> [6] default-linux/amd64/2007.0/desktop |
88 |
> [7] default-linux/amd64/2007.0/no-multilib |
89 |
> [8] default-linux/amd64/2007.0/server |
90 |
> [9] hardened/amd64 |
91 |
> [10] hardened/amd64/multilib |
92 |
> [11] selinux/2007.0/amd64 |
93 |
> [12] selinux/2007.0/amd64/hardened |
94 |
> |
95 |
> #eselect profile set 6 |
96 |
> |
97 |
> And then - sos - |
98 |
> |
99 |
> # emerge --update --deep --newuse --pretend --verbose world |
100 |
> |
101 |
> |
102 |
> Total: 478 packages (1 upgrade, 396 downgrades, 14 new, 1 in new slot, |
103 |
> 66 reinstalls, 5 blocks), Size of downloads: 480,074 kB |
104 |
> |
105 |
> so bad! :----( |
106 |
> |
107 |
> perhaps with the 2Gb of ccache that I have saved could take this process |
108 |
> only one or 2 days. |
109 |
> |
110 |
> Thank's for the tip |
111 |
> |
112 |
> |
113 |
> El mar, 29-01-2008 a las 11:22 +0000, Beso escribió: |
114 |
> > well, just removing ~amd64 from your make.conf and eselect profile set |
115 |
> > default-linux/amd64/2007.0 and then emerge -uDNvp will let you see |
116 |
> > what would compile. |
117 |
> > if you instead want to rebuild from scratch then funtoo has recent |
118 |
> > compiled stages that would let you not compile a lot of updated stuff. |
119 |
> > |
120 |
> > 2008/1/29, agtdino <agtdino@××××××××.es>: |
121 |
> > Well, my system is uptime since for a long time and has many |
122 |
> > updates |
123 |
> > more than I belive!,, :D |
124 |
> > For the moments is running well, I dont be a freek of gentoo |
125 |
> > but when I |
126 |
> > buy the amd64 system I had to make something hard step's to |
127 |
> > startit, |
128 |
> > perhaps it's not something clean and it's has profiles to the |
129 |
> > pass. |
130 |
> > I go to think in change this profile, or it reinstall from |
131 |
> > scratch ( is |
132 |
> > more fastest but the less interesting :( ) |
133 |
> > |
134 |
> > Thank's and regards |
135 |
> > |
136 |
> > El mar, 29-01-2008 a las 09:56 +0000, Beso escribió: |
137 |
> > > i think that if you're using the flags you're using you're a |
138 |
> > real |
139 |
> > > gentoo poweruser. but the fact that the profile is still set |
140 |
> > to 2006.1 |
141 |
> > > makes me wonder if you really know what you're doing... |
142 |
> > > someone who usually uses the flags you're using also uses |
143 |
> > the latest |
144 |
> > > profile. |
145 |
> > > i really think that you should update your profile (use |
146 |
> > eselect |
147 |
> > > profile to do it, i think that 2006.1 would disappear in |
148 |
> > some months) |
149 |
> > > and then compile at least the base system from the amd64 |
150 |
> > branch. then |
151 |
> > > you could use gcc-4.2.2 and other things the way you want. i |
152 |
> > > personally use a lot of unstable stuff, but the base system |
153 |
> > is amd64 |
154 |
> > > and not ~amd64. |
155 |
> > > |
156 |
> > > 2008/1/29, agtdino <agtdino@××××××××.es>: |
157 |
> > > Hello, Thank's for the response I will change kernel |
158 |
> > to |
159 |
> > > 2.6.23-r6. |
160 |
> > > |
161 |
> > > Regard's |
162 |
> > > |
163 |
> > > El mar, 29-01-2008 a las 02:31 -0600, Steev |
164 |
> > Klimaszewski |
165 |
> > > escribió: |
166 |
> > > > On Tue, 2008-01-29 at 09:17 +0100, agtdino wrote: |
167 |
> > > > > Hi, |
168 |
> > > > Hi! |
169 |
> > > > |
170 |
> > > > I am the maintainer of madwifi-ng - it is |
171 |
> > currently |
172 |
> > > incompatible (well |
173 |
> > > > there is a patch in bugzilla however it is not the |
174 |
> > proper |
175 |
> > > fix) with |
176 |
> > > > 2.6.24 - if you absolutely must have 2.6.24, then |
177 |
> > you will |
178 |
> > > need to |
179 |
> > > > compile the madwifi modules from svn, until they |
180 |
> > put out a |
181 |
> > > release |
182 |
> > > > (which *should* be soon, they are only waiting on |
183 |
> > two |
184 |
> > > patches) that is |
185 |
> > > > compatible with 2.6.24. |
186 |
> > > > |
187 |
> > > > Sorry for your troubles, for now, unless it is |
188 |
> > absolutely |
189 |
> > > necessary, I |
190 |
> > > > would suggest continuing using 2.6.23-r6 |
191 |
> > > > |
192 |
> > > > -- Steev |
193 |
> > > > |
194 |
> > > |
195 |
> > > -- |
196 |
> > > gentoo-amd64@l.g.o mailing list |
197 |
> > > |
198 |
> > > |
199 |
> > > |
200 |
> > > |
201 |
> > > -- |
202 |
> > > dott. ing. beso |
203 |
> > |
204 |
> > -- |
205 |
> > gentoo-amd64@l.g.o mailing list |
206 |
> > |
207 |
> > |
208 |
> > |
209 |
> > |
210 |
> > -- |
211 |
> > dott. ing. beso |
212 |
> |
213 |
> -- |
214 |
> gentoo-amd64@l.g.o mailing list |
215 |
> |
216 |
> |
217 |
|
218 |
|
219 |
-- |
220 |
dott. ing. beso |