Re: [gentoo-dev] Another call for BugVoting on bugs.gentoo.org

[Heinrich Wendel]

On Tuesday 17 May 2005 10:13, Brian Harring wrote:
 On Tue, May 17, 2005 at 09:58:43AM +0200, Thierry Carrez wrote:
  Stefan Schweizer wrote:
   Many bugs in bugzilla have ebuilds contributed, the work is done,
   there is just no developer to add them to the tree and review them.
   Bugvoting would allow other developers to see where they can help. For
   example I am using kde but dont read all kde bugs, so if I would know
   there is a kde bug with many votes I would maybe look at it.
 
  I have mixed feelings about this.
 
  Voting would be useful to judge which package gathers sufficient
  popularity to be added to Portage for example. Currently only packages a
  developer cares for are added, voting would help to get user opinion.
 
  On the other hand, on base system bugs for example voting would be more
  a pressure tool that might not help much...
 
  We could enable voting on a New Ebuilds section and see how it goes ?

 Seems like a good approach in my opinion.  Most of the nays have
 basically come down to I don't want people voting on stuff I'm
 working on, I know what needs to be done, don't need extra input to
 discern it.
 Ebuild submissions fall squarely outside of that arguement, and would
 be a good test run of it.

 Personally, I'd be interested in it for actual portage bugs; that
 said, I'm not totally sure if I'd want it enabled _now_ since there
 are internal changes needed rather then more feature bloat, so voting
 would be ignored till internal bits are done.

So who can make the decision here?


 My 2 cents...
 ~harring
mfg, heinrich :-)
-- 
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Another call for BugVoting on bugs.gentoo.org

[Heinrich Wendel]

I just read this: http://www.kdedevelopers.org/node/view/1055 and think it 
explains things very well.

So here is just another call for enabling bug voting on bugs.gentoo.org

mfg, heinrich :-)
-- 
gentoo-dev@gentoo.org mailing list

[gentoo-dev] Portage ebuild cruft

[Heinrich Wendel]

Hi,

Portage is slow? How to make it faster? By removing unused ebuilds!

I wrote a little script to check which ebuilds in portage aren't used 
anylonger, here the result:

Total packages checked: 9076
Total ebuilds checked: 18662
Total ebuilds to remove: 4643

Of course the script can't detect every ebuild situation, so take the numbers 
with care. But still it shows that 1/4 of all ebuilds could be removed. This 
would improve portage performance by at least 1/4, so developers go ahead. 
The script is attached, just run it as if it was repoman, it won't do 
anything, just show the orphaned packages.

mfg, heinrich :-)


cleanup.py
Description: application/python