Hi all, A friend of mine and myself are willing to develop some tools to help ebuild development.
We have some constraints, but we are thinking on something like: 1) A tool to ease writing ebuilds. It would take some parameters, i.e.: 1.1) Where are the sources? 1.2) Decompression algorithm? 1.3) Compile the sources? 1.4) Install man page(s)? 1.5) Install documentation? 1.6) Bind actions to USE flags? It would probably be interesting to define a set of pre-defined categories: standard GNU Autotools projects, perl/CPAN modules, python, ... 2) A tool to deal with the unstandarized way to compile and install Java projects. The idea is to write a tool to try to find out: 2.1) Where are located the "main" .java sources. 2.2) Where are located the unit tests. 2.3) Where are the jar files generated (in case of Ant-based builds) when the project is built. 2.4) Where to get the dependencies. And once this information is available, fill the blanks of a pre-defined Maven2 pom.xml descriptor, and use it to drive the ebuild. This way it would allow compilation flags even if the original build mechanism didn't. We probably will ask for this specific issue to gentoo-java mailing list. We don't think a fully-automated tool is feasible to cope with all kind of projects, but we hope it could be of use for Java developers who don't use Gentoo but find interesting to get an ebuild with little effort. However, we are just in the definition stage. We haven't decided anything yet, and would like to know your suggestions, even if they aren't encouraging :). Thank you very much. Jose.
pgpnYTOLxqU3C.pgp
Description: PGP signature
