-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thu, 26 Aug 2004 15:21:21 +0200, Marcus Crafter <[EMAIL PROTECTED]> wrote:
> Hi Arnaud, Hi Marcus, > On Thu, 2004-08-26 at 01:13, Arnaud Vandyck wrote: [...] >> You can also refer to this page where I did preliminary work: >> http://people.debian.org/~avdyk/maven.html > > Great, thanks for the pages. No problem, feel free to copy/modify them, add a wiki page at http://java.debian.net if you wanna coordinate the work. >> Don't forget you need to build maven from sources with libraries >> existing in Debian (not the one provided by upstream!)... so you need >> first to identify all the libs used by Maven and then package them for >> Debian if they are not yet. > > Ouch - is this in the Java policy? No, it's in the Debian policy ;-) ,----[ /usr/share/doc/debian-policy/policy.txt.gz ] | 2.2.1. The main section | ----------------------- | | Every package in _main_ and _non-US/main_ must comply with the DFSG | (Debian Free Software Guidelines). | | In addition, the packages in _main_ | * must not require a package outside of _main_ for compilation | or execution (thus, the package must not declare a "Depends", | "Recommends", or "Build-Depends" relationship on a non-_main_ | package), | * must not be so buggy that we refuse to support them, and | * must meet all policy requirements presented in this manual. `---- > Does this need to be satisfied before you make your first upload, or > can we refine the package and their dependencies as a continual > process over time? Are you in a hurry? I do prefer we take our time but make things the best possible. From my experience, if you do an upload without packaging required libraries, nobody will package them in the future. See the 'log4j should be built from sources' in the BTS (liblog4j1.2-java). > For something like maven this could be quite a few packages. Yes it is. I already begun the work, but there are a lot of problems with Maven I'll explain later. > Something else to think about are (future) packages that are built with > Maven, (eg most of the jakarta commons and codehaus, etc code). ATM, we do not use Maven to build them and it should not be needed. Ant is good enough. > Maven will generally download all dependencies during build time > unless we make it run in offline mode I did not know about the offline mode. It's not acceptable for Debian to relay on a network to build something. > however we have (atm) no automated way of currently building a local > maven repository from Build-Depends-Indep java packages.... but we have ant that can already do this. >> For any java package in Debian, you can find useful tips at the pkg-java >> Alioth's project: >> http://pkg-java.alioth.debian.org/ > > Cool - thanks for that, subscribing to the java maintainers mailing list > now.. Every DD (or even non-DD) interested in Java packaging is highly welcome ;-) The battle for Maven in Debian - ------------------------------ If we want Maven in Debian, we have some question to resolve before doing that. NOTE: I have this email for days but never find the time to end it! So here it comes and sorry if it's incomplete :( Cheers, - -- .''`. : :' :rnaud `. `' `- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBVDzl4vzFZu62tMIRAmoKAJ9ro/bKY+XtHHdvZfoApNGieqOCXACgsFQb cEo1cDM0kdmuVz0HgyF/Xqw= =ufDY -----END PGP SIGNATURE-----
