On Fri, 2006-06-09 at 10:28 +0200, Patrick Lauer wrote: > > > > Except that I can *look* at an ebuild without having to break out a > > > > subversion client currently. > > > See my answer in 3) > > See mine. ;] > Hmmm ... bugzilla. > Instead of a simple cvs up; cd /usr/local/portage/category/package I > need to search for ALL bugs with $name in it, look which one it is, > curse bugzilla for falling asleep again, see which attachments are > relevant, download them, curse bugzilla for falling asleep again, copy > them to my overlay, read the bugcomments to see if any special renaming > or directory structure is needed ... > > Hmmm. I think an overlay does have some advantages there ...
Advantages? With bugzilla I: search for the bug, cc myself on it, download the relevant files, look over them, note a style error, try to merge it, fix a compilation bug, re-upload the fixed ebuild and patch to bugzilla with a comment to the ebuild author on their mistake. When an update hits my inbox I can go directly to the bug... With an overlay: search sunrice.gentoo.org for the package (no, I don't know category/name), sync that directory (no, I'm not syncing the whole sunrice tree), check it over, note some mistakes, compile it if I feel OK with it, it fails, I fix it - and what then? Where do I discuss the problems? How do I get my fixes to other users, considering the package is devless and the b.g.o bug is out of date? If I open a b.g.o bug, will it be read? This seems like *raising* the barrier to entry to me... Ed -- gentoo-dev@gentoo.org mailing list
