| Summary: | kio_sword application: new ebuild | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Bettler <thomas.bettler> |
| Component: | Current packages | Assignee: | Jon Hood (RETIRED) <squinky86> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | squinky86 |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://lukeplant.me.uk/kio-sword/ | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
kio_sword-0.1.ebuild
kio_sword-0.2.ebuild kio_sword-0.2-r1.ebuild |
||
|
Description
Thomas Bettler
2005-04-10 05:03:12 UTC
Created attachment 55854 [details]
kio_sword-0.1.ebuild
*** Bug 89177 has been marked as a duplicate of this bug. *** Created attachment 76435 [details]
kio_sword-0.2.ebuild
Version bump
Works fine for me with kde-3.5
Added ~amd64 to ebuild and bumped to kio_sword-0.2-r1.ebuild. Would be great to get this in portage. (Since it works with sword which is already in) Created attachment 76911 [details]
kio_sword-0.2-r1.ebuild
Works on amd64 so added ~amd64 to arch.
Why can't we use epatch? The only thing he added was ~amd64. No need for a patch, or you mean something else? For the sake of consistency, the line in src_unpack() that performs the patch command should be changed to "epatch" and then the path to the patch file. I think this should work... KDE team, could I please get permission to put this under the kde herd of packages and list myself as maintainer, or is there some other format that y'all prefer non-kde-herd-members to follow before submitting kde-related packages? Thanks for the info Flameyes; I'll go ahead and finish testing and add this to portage in the next couple days. (01:06:36) Flameeyes: no problem with putting it into kde herd listing you as maintainer And I say no. It's absolutely fine, if you want maintain it, but either add yourself to the kde alias or don't put kde as maintainer herd into metadata.xml. Having to forward bugs sucks. Thanks for the ebuild. It's now in portage with a few minor alterations: 1) used epatch so that it would be consistent with other packages in portage 2) changed the name to kio-sword so that it would be consistent with other kio packages 3) took out dependency on sword-modules. While it is pointless to use this without modules, requiring every user to download the currently heafty sword-modules package is not so nice. A note is shown to the user to remind them to install modules, either manually or using the ebuild. This is an excellent package and good work done on the ebuild; I'll be using this one a lot; thanks for the submission, and I appologize for the long wait time in getting it into portage. |