Re: [gentoo-user] Portage option "--changed-use" not working?
Hilco Wijbenga wrote: > Hi all, > > In "man emerge" I read: > > --changed-use > Tells emerge to include installed packages where USE flags have > changed since installation. This option also implies the --selective > option. Unlike --newuse, the --changed-use option does not trigger > reinstallation when flags that the user has not enabled are added or > removed. > > So I always include "--changed-use" when upgrading @world. But with > the removal of kdeenablefinal I now get 150 reinstalls with > changed-use. This seems to be contradicting the man page? Or am I > misunderstanding things? Or did I misconfigure something? To be clear, > I have never enabled kdeenablefinal. > > The full command I usually run is > > emerge --verbose --deep --with-bdeps=y --complete-graph --update > --changed-use --keep-going world > > should that be relevant. > > Cheers, > Hilco > > To update, it appears this was a bug and Zac has fixed it. This is from -dev: On 01/20/2012 10:28 AM, Hilco Wijbenga wrote: > I'd like to chime in here. I started a thread on gentoo-user (Portage > option "--changed-use" not working?) pretty much about this. > > I use --changed-use instead of --newuse to get the advantages of a > fully up-to-date system without the unnecessary churn. From the man > page I understand that (part of) the idea behind --changed-use is to > *not* rebuild packages where an unused/disabled USE flag is dropped. > Which ought to apply to kdeenablefinal, right? > > It seems my understanding is incorrect because I see --new-use + > --exclude is being recommended, not --changed-use. Would somebody > please set me straight? You've found a bug. It's fixed in git now: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=a77292d37e3c2604479514abed2dda64dabace25 As a workaround, you can add --binpkg-respect-use=n to your options. -- Thanks, Zac So, it will work like it should pretty soon. Things are getting better. Gentoo has been doing that for years anyway. lol Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
Re: [gentoo-user] Portage option "--changed-use" not working?
Neil Bothwick wrote: > On Fri, 20 Jan 2012 04:08:57 -0600, Dale wrote: > Sometimes my problem is it is like shooting skeet, it's a moving target. Sometimes it moves pretty darn fast too. Zac adds it faster than I can keep up. I wish they would announce new stuff when it get released, both unstable and stable. Then again, maybe it moves so fast he can't keep up either. lol >>> >>> --changed-use has been around for many years. > >> It sounds like the way it works has changed tho. I don't think I >> have used that option before so I don't know how it used to work. >> I think the OP thinks the same. Something changed I guess. We >> all know that after the build output disappeared a while back. > > It hasn't changed and generally works as expected. I suspect this > is specific to the KDE ebuilds (or eclass). changed-use should only > skip an ebuild with changed flags if re-emerging would produce > exactly the same code as before, this may not be the case. For > example, in some ebuilds, it is the absence of a USE flag that > triggers an extra configure option, so removing that use flag would > give the same code as if the package had been emerged with it > enabled. > > Something like this happened recently with the nls flag on glibc. > > I'll take your word for it. ;-) Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
Re: [gentoo-user] Portage option "--changed-use" not working?
On Fri, 20 Jan 2012 04:08:57 -0600, Dale wrote: > >> Sometimes my problem is it is like shooting skeet, it's a moving > >> target. Sometimes it moves pretty darn fast too. Zac adds it > >> faster than I can keep up. I wish they would announce new stuff > >> when it get released, both unstable and stable. Then again, > >> maybe it moves so fast he can't keep up either. lol > > > > --changed-use has been around for many years. > It sounds like the way it works has changed tho. I don't think I have > used that option before so I don't know how it used to work. I think > the OP thinks the same. Something changed I guess. We all know > that after the build output disappeared a while back. It hasn't changed and generally works as expected. I suspect this is specific to the KDE ebuilds (or eclass). changed-use should only skip an ebuild with changed flags if re-emerging would produce exactly the same code as before, this may not be the case. For example, in some ebuilds, it is the absence of a USE flag that triggers an extra configure option, so removing that use flag would give the same code as if the package had been emerged with it enabled. Something like this happened recently with the nls flag on glibc. -- Neil Bothwick Idaho - It's not the end of the world, but you can see it from there. signature.asc Description: PGP signature
Re: [gentoo-user] Portage option "--changed-use" not working?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Neil Bothwick wrote: > On Fri, 20 Jan 2012 03:07:18 -0600, Dale wrote: > >> Sometimes my problem is it is like shooting skeet, it's a moving >> target. Sometimes it moves pretty darn fast too. Zac adds it >> faster than I can keep up. I wish they would announce new stuff >> when it get released, both unstable and stable. Then again, >> maybe it moves so fast he can't keep up either. lol > > --changed-use has been around for many years. > > It sounds like the way it works has changed tho. I don't think I have used that option before so I don't know how it used to work. I think the OP thinks the same. Something changed I guess. We all know that after the build output disappeared a while back. Dale :-) :-) - -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n" -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8ZPTkACgkQiBoxVpK2GMDCMQCfUzkiAiQpKZsfWzDyDKe2PEfS BJYAoLIpyMzkteuaTauSAgVY/Eh7YotY =WNq0 -END PGP SIGNATURE-
Re: [gentoo-user] Portage option "--changed-use" not working?
On Fri, 20 Jan 2012 03:07:18 -0600, Dale wrote: > Sometimes my problem is it is like shooting skeet, it's a moving target. > Sometimes it moves pretty darn fast too. Zac adds it faster than I can > keep up. I wish they would announce new stuff when it get released, > both unstable and stable. Then again, maybe it moves so fast he can't > keep up either. lol --changed-use has been around for many years. -- Neil Bothwick *Libra*: /(Sept 23--Oct 23)/ An unfortunate typo on your application results in your being accepted into the Legion Of Superherpes. signature.asc Description: PGP signature
Re: [gentoo-user] Portage option "--changed-use" not working?
Hilco Wijbenga wrote: > On 19 January 2012 19:25, Dale wrote: >> Hilco Wijbenga wrote: >>> On 19 January 2012 17:38, Dale wrote: Hilco Wijbenga wrote: > On 19 January 2012 16:05, Dale wrote: >> Well, the USE flag got changed. Isn't that what -N is supposed to do? > > -N == --newuse not --changed-use :-) > > It's exactly for this reason that I use --changed-use and not > --newuse. See the man page for the details. > > Well, sort of seems like about the same. The dev changed the USE flag, it is changed, portage sees it was changed, portage wants to recompile it with the new/changed flags. I'm not exactly clear on the difference between newuse and changed-use. If you enable a USE flag, it is changed. If you disable a USE flag, it is changed. If a new flag comes along and it is different than the last install, then it can be either a new flag or a changed flag. It should recompile either way. >>> >>> The point here is that a USE flag was removed but it wasn't enabled >>> anyway. So no recompile necessary. Which is what --changed-use is >>> supposed to be for (as I understand the man page). >>> Maybe there is some subtle difference somewhere that I am missing. >>> >>> Which is why I included what it says in the man page and then referred >>> you to said man page... ;-) >>> >>> >> >> >> Well, when I did mine, it showed up as a change. It was in yellow. >> Maybe your system was different or something. > > Nope, same here. And obviously there was a change: a flag was removed. > But, again, my understanding of --changed-use (as opposed to --newuse) > is that it should have prevented the reinstall. > >> Most man pages are Greek. My Greek is not real good. > > :-) I don't think they're quite that bad although I agree that you > sometimes sort of already need to know where to look. > > Sometimes my problem is it is like shooting skeet, it's a moving target. Sometimes it moves pretty darn fast too. Zac adds it faster than I can keep up. I wish they would announce new stuff when it get released, both unstable and stable. Then again, maybe it moves so fast he can't keep up either. lol Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
Re: [gentoo-user] Portage option "--changed-use" not working?
On 19 January 2012 19:25, Dale wrote: > Hilco Wijbenga wrote: >> On 19 January 2012 17:38, Dale wrote: >>> Hilco Wijbenga wrote: On 19 January 2012 16:05, Dale wrote: > Well, the USE flag got changed. Isn't that what -N is supposed to do? -N == --newuse not --changed-use :-) It's exactly for this reason that I use --changed-use and not --newuse. See the man page for the details. >>> >>> >>> Well, sort of seems like about the same. The dev changed the USE flag, >>> it is changed, portage sees it was changed, portage wants to recompile >>> it with the new/changed flags. >>> >>> I'm not exactly clear on the difference between newuse and changed-use. >>> If you enable a USE flag, it is changed. If you disable a USE flag, it >>> is changed. If a new flag comes along and it is different than the last >>> install, then it can be either a new flag or a changed flag. It should >>> recompile either way. >> >> The point here is that a USE flag was removed but it wasn't enabled >> anyway. So no recompile necessary. Which is what --changed-use is >> supposed to be for (as I understand the man page). >> >>> Maybe there is some subtle difference somewhere that I am missing. >> >> Which is why I included what it says in the man page and then referred >> you to said man page... ;-) >> >> > > > Well, when I did mine, it showed up as a change. It was in yellow. > Maybe your system was different or something. Nope, same here. And obviously there was a change: a flag was removed. But, again, my understanding of --changed-use (as opposed to --newuse) is that it should have prevented the reinstall. > Most man pages are Greek. My Greek is not real good. :-) I don't think they're quite that bad although I agree that you sometimes sort of already need to know where to look.
Re: [gentoo-user] Portage option "--changed-use" not working?
Hilco Wijbenga wrote: > On 19 January 2012 17:38, Dale wrote: >> Hilco Wijbenga wrote: >>> On 19 January 2012 16:05, Dale wrote: Well, the USE flag got changed. Isn't that what -N is supposed to do? >>> >>> -N == --newuse not --changed-use :-) >>> >>> It's exactly for this reason that I use --changed-use and not >>> --newuse. See the man page for the details. >>> >>> >> >> >> Well, sort of seems like about the same. The dev changed the USE flag, >> it is changed, portage sees it was changed, portage wants to recompile >> it with the new/changed flags. >> >> I'm not exactly clear on the difference between newuse and changed-use. >> If you enable a USE flag, it is changed. If you disable a USE flag, it >> is changed. If a new flag comes along and it is different than the last >> install, then it can be either a new flag or a changed flag. It should >> recompile either way. > > The point here is that a USE flag was removed but it wasn't enabled > anyway. So no recompile necessary. Which is what --changed-use is > supposed to be for (as I understand the man page). > >> Maybe there is some subtle difference somewhere that I am missing. > > Which is why I included what it says in the man page and then referred > you to said man page... ;-) > > Well, when I did mine, it showed up as a change. It was in yellow. Maybe your system was different or something. Most man pages are Greek. My Greek is not real good. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
Re: [gentoo-user] Portage option "--changed-use" not working?
On 19 January 2012 17:38, Dale wrote: > Hilco Wijbenga wrote: >> On 19 January 2012 16:05, Dale wrote: >>> Well, the USE flag got changed. Isn't that what -N is supposed to do? >> >> -N == --newuse not --changed-use :-) >> >> It's exactly for this reason that I use --changed-use and not >> --newuse. See the man page for the details. >> >> > > > Well, sort of seems like about the same. The dev changed the USE flag, > it is changed, portage sees it was changed, portage wants to recompile > it with the new/changed flags. > > I'm not exactly clear on the difference between newuse and changed-use. > If you enable a USE flag, it is changed. If you disable a USE flag, it > is changed. If a new flag comes along and it is different than the last > install, then it can be either a new flag or a changed flag. It should > recompile either way. The point here is that a USE flag was removed but it wasn't enabled anyway. So no recompile necessary. Which is what --changed-use is supposed to be for (as I understand the man page). > Maybe there is some subtle difference somewhere that I am missing. Which is why I included what it says in the man page and then referred you to said man page... ;-)
Re: [gentoo-user] Portage option "--changed-use" not working?
Hilco Wijbenga wrote: > On 19 January 2012 16:05, Dale wrote: >> Well, the USE flag got changed. Isn't that what -N is supposed to do? > > -N == --newuse not --changed-use :-) > > It's exactly for this reason that I use --changed-use and not > --newuse. See the man page for the details. > > Well, sort of seems like about the same. The dev changed the USE flag, it is changed, portage sees it was changed, portage wants to recompile it with the new/changed flags. I'm not exactly clear on the difference between newuse and changed-use. If you enable a USE flag, it is changed. If you disable a USE flag, it is changed. If a new flag comes along and it is different than the last install, then it can be either a new flag or a changed flag. It should recompile either way. Maybe there is some subtle difference somewhere that I am missing. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
Re: [gentoo-user] Portage option "--changed-use" not working?
On 19 January 2012 16:05, Dale wrote: > Well, the USE flag got changed. Isn't that what -N is supposed to do? -N == --newuse not --changed-use :-) It's exactly for this reason that I use --changed-use and not --newuse. See the man page for the details.
Re: [gentoo-user] Portage option "--changed-use" not working?
Hilco Wijbenga wrote: > On 19 January 2012 14:28, Dale wrote: >> Hilco Wijbenga wrote: >>> Hi all, >>> >>> In "man emerge" I read: >>> >>> --changed-use >>> Tells emerge to include installed packages where USE flags have >>> changed since installation. This option also implies the --selective >>> option. Unlike --newuse, the --changed-use option does not trigger >>> reinstallation when flags that the user has not enabled are added or >>> removed. >>> >>> So I always include "--changed-use" when upgrading @world. But with >>> the removal of kdeenablefinal I now get 150 reinstalls with >>> changed-use. This seems to be contradicting the man page? Or am I >>> misunderstanding things? Or did I misconfigure something? To be clear, >>> I have never enabled kdeenablefinal. >>> >>> The full command I usually run is >>> >>> emerge --verbose --deep --with-bdeps=y --complete-graph --update >>> --changed-use --keep-going world >>> >>> should that be relevant. >>> >>> Cheers, >>> Hilco >>> >>> >> >> >> Just to be clear, it was a dev that changed the kdeenablefinal flag. It >> was sort of discussed on -dev. I think the dev that did it doesn't use >> -N so it doesn't affect him and I guess he thinks it won't affect others >> either. > > I know and I don't mind the kdeenablefinal flag being removed. That > makes perfect sense. > > It's just that --changed-use ought to have prevented the 150 > unnecessary reinstalls. Or at least, I think it should have. :-) > > Well, the USE flag got changed. Isn't that what -N is supposed to do? Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
Re: [gentoo-user] Portage option "--changed-use" not working?
On 19 January 2012 14:28, Dale wrote: > Hilco Wijbenga wrote: >> Hi all, >> >> In "man emerge" I read: >> >> --changed-use >> Tells emerge to include installed packages where USE flags have >> changed since installation. This option also implies the --selective >> option. Unlike --newuse, the --changed-use option does not trigger >> reinstallation when flags that the user has not enabled are added or >> removed. >> >> So I always include "--changed-use" when upgrading @world. But with >> the removal of kdeenablefinal I now get 150 reinstalls with >> changed-use. This seems to be contradicting the man page? Or am I >> misunderstanding things? Or did I misconfigure something? To be clear, >> I have never enabled kdeenablefinal. >> >> The full command I usually run is >> >> emerge --verbose --deep --with-bdeps=y --complete-graph --update >> --changed-use --keep-going world >> >> should that be relevant. >> >> Cheers, >> Hilco >> >> > > > Just to be clear, it was a dev that changed the kdeenablefinal flag. It > was sort of discussed on -dev. I think the dev that did it doesn't use > -N so it doesn't affect him and I guess he thinks it won't affect others > either. I know and I don't mind the kdeenablefinal flag being removed. That makes perfect sense. It's just that --changed-use ought to have prevented the 150 unnecessary reinstalls. Or at least, I think it should have. :-)
Re: [gentoo-user] Portage option "--changed-use" not working?
Hilco Wijbenga wrote: > Hi all, > > In "man emerge" I read: > > --changed-use > Tells emerge to include installed packages where USE flags have > changed since installation. This option also implies the --selective > option. Unlike --newuse, the --changed-use option does not trigger > reinstallation when flags that the user has not enabled are added or > removed. > > So I always include "--changed-use" when upgrading @world. But with > the removal of kdeenablefinal I now get 150 reinstalls with > changed-use. This seems to be contradicting the man page? Or am I > misunderstanding things? Or did I misconfigure something? To be clear, > I have never enabled kdeenablefinal. > > The full command I usually run is > > emerge --verbose --deep --with-bdeps=y --complete-graph --update > --changed-use --keep-going world > > should that be relevant. > > Cheers, > Hilco > > Just to be clear, it was a dev that changed the kdeenablefinal flag. It was sort of discussed on -dev. I think the dev that did it doesn't use -N so it doesn't affect him and I guess he thinks it won't affect others either. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS="--quiet-build=n"
[gentoo-user] Portage option "--changed-use" not working?
Hi all, In "man emerge" I read: --changed-use Tells emerge to include installed packages where USE flags have changed since installation. This option also implies the --selective option. Unlike --newuse, the --changed-use option does not trigger reinstallation when flags that the user has not enabled are added or removed. So I always include "--changed-use" when upgrading @world. But with the removal of kdeenablefinal I now get 150 reinstalls with changed-use. This seems to be contradicting the man page? Or am I misunderstanding things? Or did I misconfigure something? To be clear, I have never enabled kdeenablefinal. The full command I usually run is emerge --verbose --deep --with-bdeps=y --complete-graph --update --changed-use --keep-going world should that be relevant. Cheers, Hilco
