On 11/2/2013 07:04, hasufell wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Another round of questioning the users here.
These are good, thank you. Short answer here is no.


more specifically:
* how often do you experience useless rebuilds?
At least one of my machines is constantly wanting to rebuild some package or another. Currently, one of my desktops wants to rebuild x11-misc/compton with every emerge.

* do you really have a problem with running
revdep-rebuild/haskell-updater/perl-cleaner etc after every emerge?
No, because I typically understand when they're needed and can predict when I should use them, which really isn't all that often.

* do you think it's worth the effort to add more stuff to the PM, so
that you don't have to run revdep-rebuild that often?
I think we should have stopped at @preserved-rebuild. It's a sort of middle ground between rebuilding things all the time and having a broken system. I like it because it allows me to leave some things in a semi-broken state until I have time and CPU cycles to dedicate to rebuild them (i.e. libreoffice, etc.).

* do you trust the other methods like subslots or preserved-rebuild to
work reliably? (as in: do you still use revdep-rebuild?)
I've been using preserved-rebuild ever since it was backported to 2.1, and I don't think I've needed revdep-rebuild since then. I run it occasionally, but it's never found anything.


If you want my opinion on subslots:
# grep EMERGE_DEFAULT_OPTS /etc/portage/make.conf
EMERGE_DEFAULT_OPTS="--ignore-built-slot-operator-deps=y"
I'm getting closer to this sentiment as well; I'm beginning to think they're more trouble than they're worth. I'm getting tired of seeing an emerge list of 10 or 15 rebuilds when I'm trying to install something brand new because some package in the tree I already have installed has changed. If I cared about that package and its dependencies, I would have asked for it to be rebuilt/upgraded/whatever, but I don't, I'm working on something else right now.

--
♫Dustin
http://dustin.hatch.name/

Reply via email to