On Sat, 11 Mar 2006 13:28:45 -0800, James Colannino wrote: > I went ahead and posted the ebuild on bugzilla > (https://bugs.gentoo.org/show_bug.cgi?id=124985) Anybody who's > interested in it can download it from there. Don't forget to manually > download courier-imap-4.1.0.tar.bz2 from http://courier-mta.org/imap/ > and run ebuild digest on it if you decide to use it. > > James
A few notes on your bugzilla submission. 1) The component should be Ebuild 2) After you submit the original bug, edit the Keywords field and add EBUILD and submit again. I know, it's redundant, but that's the way it's supposed to be done. Bugzilla should have more fields open on the original submission page. 3) Your summary should contain a little more info, like (NEW EBUILD) or (VERSION BUMP) along with the category the ebuild should belong too. Something like this: /net-mail/courier-imap-4.1.0 (VERSION BUMP) This helps the bug wranglers properly assign the bug. You also could view the changelog and email the maintainer privately with this request. Something as simple as renaming an ebuild for a new version could occur quickly. The 3rd line, # $Header: $ needs to end with a $ after the : and space. The /var/cvsroot stuff does not apply for new ebuilds until the maintainer publishes it. Lastly, I notice that there are a fair amount of patches going on, and with these you need to be very careful. The patches should be examined against the new files and make sure they are even required. Sometimes, simply renaming a file is insufficient. I hope you don't mind these comments. They are designed to protect you from the wrath of the bug wranglers who have a low tolerance threshold sometimes for incorrectly submitted bugs. I know! http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 should help you more. Regards -- Peter -- gentoo-user@gentoo.org mailing list
