Summary: | frobtads-0.10.ebuild (Update) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nikos Chantziaras <realnc> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.tads.org/frobtads.htm | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
frobtads-0.10.ebuild
TADS 3 Freeware Source Code License |
Description
Nikos Chantziaras
2008-04-11 00:15:01 UTC
Created attachment 149353 [details]
frobtads-0.10.ebuild
Created attachment 149355 [details]
TADS 3 Freeware Source Code License
The license of the package. This should eventually become /usr/portage/licenses/TADS.
As you referenced the bug that this is a duplicate of...please post any updates on that bug. There is no guarantee that this package will make it into the tree. A developer will have to take responsibility for it. If you want, you can maintain it in our official user overlay (http://www.gentoo.org/proj/en/sunrise/). *** This bug has been marked as a duplicate of bug 149764 *** (In reply to comment #3) > As you referenced the bug that this is a duplicate of...please post any updates > on that bug. I followed this guide before posting: http://www.gentoo.org/doc/en/ebuild-submit.xml It says to submit a new bug tagged with "(Update)" rather than posting in an existing bug. I'm a bit confused about when to post "(Update)" tagged bugs and when to reply to existing bugs. Nikos, it looks like that documentation page was last updated in 2005, unfortunately. Since it's clearly incorrect, best thing would be to submit a bug for it. Gah, I wish someone commented on this sooner :P I've posted a new ebuild in a new bug 217341 (for another package) rather than using the existing bug 66189. So the current policy is to always post in existing bugs when submitting ebuilds for new upstream versions? |