Bug 136991

Summary:	Behaviour of the kdeenablefinal USE flag
Product:	Gentoo Linux	Reporter:	Farid <djfarid>
Component:	New packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	esigra
Priority:	Low
Version:	2006.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Farid 2006-06-16 08:17:56 UTC

I had the USE flag kdeenablefinal enabled on my system. While emerging KDE, I noticed that the compile was really slow and the whole system was unusable while compiling. So I disabled the flag and restarted the compile. It went much better this time.

All good until I do an "emerge --newuse --pretend world". Emerge wants to recompile those KDE packages that got compiled with the kdeenablefinal flag set.

The binary should be exactly the same whether the kdeenablefinal flag is set or not. So re-compiling any package just because this flag changed is just waste of time.

emerge --newuse should ignore this flag in my opinion. It would maybe be useful to have a config file with all the flags that should be ignored for --newuse. Or maybe just not record whether this flag was set or not while compiling?

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2006-06-16 08:23:25 UTC

Not portage.

Comment 2 Jakub Moc (RETIRED) gentoo-dev

2006-06-16 08:24:10 UTC


*** This bug has been marked as a duplicate of 81405 ***

Comment 3 Zac Medico gentoo-dev

2006-06-16 08:40:45 UTC

This little hack (use it at your own risk, or course) should correct the problem for you:

find /var/db/pkg -name USE | xargs sed -i "s/kdeenablefinal//g"