> versions of gcc not getting along well if x!-y. > is especially true when you consider the news item about 4.x and 4.y > process of upgrading gcc, and that means I should recompile everything. The use of the term, "unresolvable" seems a bit wrong. Generally, it's best practice to add anything to your world file that you don't want 'emerge -depclean' to remove. > compiled because they don't show up in the world file. > "unresolvable" conflicts, but using emerge -ave1 world means packages NOT When using -1 (one-shot), the world file shrinks. Maybe make working with the set a little more forgiving, or perhaps integrate stale package removal as a part of the set itself. If you can give proceed at your own rish warnings for other things, why not for the set? That way, anyone who whines gets to get treated to a dose of "talk to the hand".ħ. I'm betting if that's actually done, your issues with the set will melt away like snow on a Texas highway in August.Ħ. Maybe make it so that auto-cleaning packages is more than a question I get asked when there's nothing new to emerge. Perhaps a bit of thought should be given to actually making it a bit easier to at least get rid of dead packages attached to dead ebuilds. depclean can get the job done, but more often than not, it misses crap and nukes good. On a system with 1400 packages, that's a pretty significant number of unclean files cluttering up my hard drive.ĥ. 2009! We're talking at least three hundred packages. When I went through my /var/db/pkg directory, I was stunned at the amount of files that had not been recompiled since 2009. If portage did a better job of cleaning dead packages with dead ebuilds, the problems that arise with the use of the set would be negligible. I've had one of my installs going since 2009, and it's stayed stable partly because I recompile everything, or at least thought I was until a few days ago.Ĥ. Is there another way to recompile everything if you remove this? If not, then, don't remove it. Sure, that's not for the average user, but then again, Gentoo is not your average Linux distro.ģ. I've nuked hundreds, literally HUNDREDS of stale packages of this type from my machines.Īfter that work, yes, I can say that the issues are resolvable, if you're willing to put in the effort to make it happen. That means I've been having to use the set quite a bit, if only to hunt down STALE packages without ebuilds.
This is especially true when you consider the news item about 4.x and 4.y versions of gcc not getting along well if x!-y. I have been in the process of upgrading gcc, and that means I should recompile everything. This is good for "unresolvable" conflicts, but using emerge -ave1 world means packages NOT compiled because they don't show up in the world file.Ģ.
`emerge -uDpN -with-bdeps` give an empty list It can succeed only if *all* the packages are up to date, i.e.
Attachment tamer uninstall install#
> emerge -pvKe -with-bdeps=y it's useful to know exactly which packages ARE installed, not which the package manager think should be, portage keep a database of them in /var/db/pkg, the following command create a list of these, it's ordered by time of install (ls -tr), changing "-ctime +0" to any number of days skip the packages installed in that period.įind /var/db/pkg -name BUILD_TIME -ctime +0 -exec ls -1tr ::: $(< /etc/portage/world-rebuild) > Whether I would do something like that after removing the set? I'm using a set to check the consistency of the binary packages
0 kommentar(er)
