| Summary: | sabbu-0.2.5 (new package) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Vadim Berezniker <kryptolus> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | CC: | media-video |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://www.sabbu.com | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | sabbu 0.2.5 ebuild | ||
|
Description
Vadim Berezniker
2005-07-08 21:37:34 UTC
Created attachment 62981 [details]
sabbu 0.2.5 ebuild
Is there anything I can do to speed up my program getting into portage? (In reply to comment #2) > Is there anything I can do to speed up my program getting into portage? Sure, let's start with fixing the ebuild. ;) 1/ Missing header. 2/ Keywords do not follow policy. 3/ nls does not appear to be used anywhere for compile, did I miss something? Please clarify. 4/ Wrt src_compile(), either it's parallel-make compliant or not, no way between. 5/ Why does it inherit toolchain-funcs, flag-o-matic already inherits that one, and besides - I don't see it used anywhere in the ebuild. Some docs: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=3 http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 Please reopen when you have submitted a fixed ebuild. I don't have time to play around with ebuilds. I was hoping that by submitting a simple ebuild instead of just a "please add package to portage", I could make it easier for it to get added to portage. If not, then fine. Not having it in portage won't kill me. I have to say just closing the bug as WONTFIX is pretty disrespectful. He didn't just close it as WONTFIX. He gave you a list of things that would needed to be fixed before the ebuild could be included. Since we don't have a PLEASEREOPENWITHAFIXEDEBUILD resolution, we use WONTFIX. |
