On Mittwoch, 30. Januar 2008, Beso wrote:
> the real problem stands in the keyword.... the amd64 would downgrade a lot
> of stuff.... before doing it it's better to identify the normal programs,
> like kde, gnome, and similar and let them be for the moment as ~amd64....
> but at least stuff like, gcc, glibc, baselayout, kernel and some other base
> stuff should stay on the amd64 branch.... you won't be able to downgrade
> glibc so that one for the moment would stay on the unstable branch.... but
> if you don't feel in the mood to downgrade cause the  ~amd64 being to
> amd64, then just update the profile and you should see something like 100
> packages....
> also adding --as-needed as LDFLAGS should help you save some time in
> recompiling stuff....

yeah - no. Don't do it. It breaks stuff.

> the 2gb of ccache would help, but not a lot.... 400+ packages would mean
> about 3-4 days on a amd64 2ghz single core, so prepare for a looong time of
> compile time.... also the 5 blockers are not good and should be fixed in
> some way before proceeding to the recompile....

no, it would mean something around 12h. Depending on the packages.


> if you decide to modify the use flags when changing profile it's the best
> time....

yeah, check which flags changed, and which ones you really need. That way you 
might be able to cut down the amount of packages.

> so my advice is the following:
> 1. take some time to look at the use flags (emerge ufed and see a
> description of them and also add/remove them from the ufed gui in
> make.conf) 
> 2. add LDFLAGS="--as-needed" into make.conf 

really, don't do it.

> > Total: 478 packages (1 upgrade, 396 downgrades, 14 new, 1 in new slot,
> > 66 reinstalls, 5 blocks), Size of downloads: 480,074 kB

check your keywords - and blockers are easily solved. Usually you need to 
unmerge something. And the blocking ebuild tells you what.


And agtdino and Beso:

DO NOT TOP POST.

This is not a Windows mailing list.
-- 
[email protected] mailing list

Reply via email to