Summary: | New ebuild: po4a (po for anything) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jordi Vilalta <jvprat> |
Component: | New packages | Assignee: | Michael Cummings (RETIRED) <mcummings> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | dragonheart, perl |
Priority: | High | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://alioth.debian.org/projects/po4a | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 47788 | ||
Bug Blocks: | |||
Attachments: |
The proposed ebuild
Fixed ebuild New version 0.17.1 New version 0.17.2 New version 0.18 New version 0.18.1 po4a-0.18.1.ebuild po4a-0.19.ebuild |
Description
Jordi Vilalta
2004-06-25 07:49:58 UTC
Created attachment 34136 [details]
The proposed ebuild
I only put the ~x86 flag because it's the only one where I could test the
ebuild, but the program itself is known to work in many architectures.
Things you probably want to change: 1. Use ${PN} and ${PV} inside SRC_URI, don't hardcode names or versions 2. What's the first line of src_compile doing? 3. Wrong copyright header -- as of ~yesterday we're "Gentoo Foundation" Created attachment 34146 [details]
Fixed ebuild
1. Now it uses ${PN} and ${PV} (HOMEPAGE and SRC_URI fixed)
2. What's the first line of src_compile doing? <- it was for debugging, now
it's removed
3. Copyright header changed to "Gentoo Foundation"
we can't use Gentoo Foundation yet, as we don't own yet own the copyrights I've seen there are some recent ebuilds that already use "Gentoo Foundation" (as sys-kernel/development-sources-2.6.7). Then what's the right form? skel.ebuild and everything in the tree uses Gentoo Foundation now. According to cvs log it was a combination of vapier and agriffis doing the changes. For example: date: 2004/06/24 21:57:58; author: agriffis; state: Exp; lines: +2 -2 update copyright line: Gentoo Technologies => Gentoo Foundation Created attachment 35845 [details]
New version 0.17.1
This is a new ebuild for the last release of po4a. In this version we've
updated the build system to use Module::Build (and there are a lot of bug
fixes).
sorry bugwranglers, but i don't know much about po files and have no interest in this package. please re-assign. Created attachment 37001 [details]
New version 0.17.2
New bug-fix release. It could be a pure version bump, if Alioth threw away the
damn numbers in the download url :(
Perl persons, is this ebuild done correctly (in the perl way of thinking)? It needs gettext-0.13 or later Created attachment 38284 [details]
New version 0.18
Created attachment 38370 [details]
New version 0.18.1
Can anyone explain to me how you depend on >= gettext 0.13 when it only goes up to .12? why the dep on jade when it isn't referenced by any of the documentation or deps? and then there's the missing dep...that breaks this package... OK, 'nuff ranting from the perl guy. Corrected ebuild forthcoming - would like a sign off before committing (and would appreciate comments on the gettext mismatching) Created attachment 40992 [details]
po4a-0.18.1.ebuild
Corrected deps (including typo in the actual dep line)
please ignore the commented out PN stuff - that was my using the wrong version number and not realizing it > Can anyone explain to me how you depend on >= gettext 0.13 when it only goes up to .12? It wasn't in portage, but they are at version 0.14.1: http://directory.fsf.org/localization/gettext.html It needs 0.13 when installing in order to update its own translations. This is why it depends on #47788 (that they have solved today) > why the dep on jade when it isn't referenced by any of the documentation or deps? The documented sp (James Clark's SGML parsing tools) dependency isn't in portage, so I searched for a replacement: $ qpkg -f /usr/bin/nsgmls app-text/openjade * And this is where this dep comes from ;) > and then there's the missing dep...that breaks this package... Are you talking about dev-perl/libintl-perl? This dependancy was removed in 0.18 (but we didn't document it :( ). It shouldn't break anything now. I hope it cleared some things :P yes, thank you :) ok, so as soon as the newer gettext is available this should be doable (though I had no problems on this end with what is in portage currently - current as of the third that is) Created attachment 43634 [details]
po4a-0.19.ebuild
New release.
app-text/po4a |