Summary: | mecat-1.1.ebuild (New Package) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stephan R. Palm <stephan.richard> |
Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | RESOLVED OBSOLETE | ||
Severity: | enhancement | CC: | java |
Priority: | High | Keywords: | EBUILD |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://sourceforge.net/projects/mecat/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
mecat-1.1.ebuild
mecat-1.0-gentoo.patch digest-mecat-1.1 mecat-1.1-r1.ebuild mecat-1.2.ebuild mecat-1.3.ebuild mecat-1.4.1.ebuild mecat-1.4.2 |
Description
Stephan R. Palm
2005-10-14 05:39:34 UTC
Created attachment 70655 [details]
mecat-1.1.ebuild
This is the ebuild for mecat-1.1. The ebuild needs the patch
"mecat-1.0-gentoo.patch".
Created attachment 70656 [details, diff]
mecat-1.0-gentoo.patch
Could a java guy have a look if the ebuild matches our standards, please? it doesn't Created attachment 70673 [details]
digest-mecat-1.1
(In reply to comment #5) > Created an attachment (id=70673) [edit] > digest-mecat-1.1 > You should not attach digests. Those who use ebuilds from bugzilla should now how to create them. See http://www.gentoo.org/proj/en/java/java-devel.xml for information on how to improve the ebuild. You should not do any special tricks in the ebuild for 1.5 support. We already have a generic solution to this problem, which is currently under testing. You are welcome to join the testing/documentation effort if like to get 1.5 unmasked faster. (In reply to comment #7) > See http://www.gentoo.org/proj/en/java/java-devel.xml for information on how to > improve the ebuild. You should not do any special tricks in the ebuild for 1.5 > support. We already have a generic solution to this problem, which is currently > under testing. You are welcome to join the testing/documentation effort if like > to get 1.5 unmasked faster. First of all thanks, looks like I'm not up-to-date anymore to the current events concerning Java (at least I did not find the java-devel.xml the last time I tried to commit a package for MeCat). What is the generic solution for Java 1.5 support? Afaik using 1.5 as system-wide VM results in conlict in several packages like OpenOffice. In the documentation I only find methods to "die" if Java 1.5 is not the current system-wide VM. What did I miss? For the testing/documentation effort: Where? (In reply to comment #8) > support? Afaik using 1.5 as system-wide VM results in conlict in several > packages like OpenOffice. In the documentation I only find methods to "die" if > Java 1.5 is not the current system-wide VM. What did I miss? For the > testing/documentation effort: Where? For example: http://bugs.gentoo.org/show_bug.cgi?id=65937#c30 Join #gentoo-java@freenode to get in direct contact with the java team if you have questions. "In the documentation I only find methods to "die" if Java 1.5 is not the current system-wide VM. " Where does it say that? (In reply to comment #11) > "In the documentation I only find methods to "die" if > Java 1.5 is not the current system-wide VM. " > > Where does it say that? I thought that the functionality from "java-utils.eclass" tests if the _current_ vm matches a requirement or else "die". Created attachment 70748 [details]
mecat-1.1-r1.ebuild
Redesigned ebuild.
Created attachment 95587 [details]
mecat-1.2.ebuild
New ebuild readjusted for the new java concept.
Created attachment 98734 [details]
mecat-1.3.ebuild
Ebuild for the new version 1.3 of MeCat
Created attachment 104432 [details]
mecat-1.4.1.ebuild
Ebuild for the new version of mecat
(In reply to comment #16) > Created an attachment (id=104432) [edit] > mecat-1.4.1.ebuild > > Ebuild for the new version of mecat > Some feedback to improve the ebuild: IUSE="java" Does not look like you would be using the java use flag for anything. RDEPEND=">=virtual/jre-1.5 =dev-java/xerces-2* virtual/tetex dev-tex/latex-unicode" DEPEND=">=virtual/jdk-1.5 dev-java/ant" DEPEND does not pull in for example dev-java/xerces that is needed to build this thing. Does this really need full dev-java/ant or is just dev-java/ant-core enough? If it does need the full ant, there should be a comment in the ebuild saying why it needs full ant. src_compile() { eant } You can remove this if the default target is named jar as java-pkg-2.eclass has a default src_compile function nowadays. The ebuild needs the doc and source use flags before it can be added to the tree. (In reply to comment #17) > (In reply to comment #16) > > Created an attachment (id=104432) [edit] > > mecat-1.4.1.ebuild > > > > Ebuild for the new version of mecat > > > > Some feedback to improve the ebuild: > IUSE="java" > Does not look like you would be using the java use flag for anything. And now it's gone. > RDEPEND=">=virtual/jre-1.5 > =dev-java/xerces-2* > virtual/tetex > dev-tex/latex-unicode" > > DEPEND=">=virtual/jdk-1.5 > dev-java/ant" > > DEPEND does not pull in for example dev-java/xerces that is needed to build > this thing. Does this really need full dev-java/ant or is just > dev-java/ant-core enough? If it does need the full ant, there should be a > comment in the ebuild saying why it needs full ant. just needs ant-core > src_compile() { > eant > } > > You can remove this if the default target is named jar as java-pkg-2.eclass has > a default src_compile function nowadays. Yes, nowaday ;) I've rewritten the build.xml for mecat version 1.4.2 and it has now a target jar and javadoc. > The ebuild needs the doc and source use flags before it can be added to the > tree. > Added use and source flags. Created attachment 104540 [details]
mecat-1.4.2
Ebuild for the new version of mecat.
The version that I made to include the new build.xml.
Package no longer builds. |