On Tue, Jan 05, 2010 at 09:35:04AM -0800, Kohsuke Kawaguchi wrote: > Tim Retout wrote: > > I've been using your hudson Debian packages, and it's a really useful > > piece of software. I'd like to see it in the main Debian archive - > > are you interested in working together on this? > > Yes, I'd be very happy to.
Fantastic! > It is built from the binary war file of the official Hudson releases. Okay, I found the src.zip, and that's great. I'll need to replace the debian/ directory, but that's not a problem. > I'm aware of the "build from source" policy in Debian, but how far does > it go? For example, Hudson is a Java web application, which contains a > whole bunch of other library files in it, which are built and released > by 3rd parties. Do those libraries need to be packaged separately, or do > Hudson need to rebuild them from sources? The libraries should be packaged separately - these will of course be built from source in the other packages, but the hudson package won't worry about them. > Hudson also uses Maven as the build tool, and as you may already know, > it comes with a built-in mechanism to download all kinds of stuff (that > it uses during the build) from the internet. Do those also have to be > packaged separately or be built from the source? The build dependencies will be packaged separately as well. > Alternatively, does Debian have anything like Ubuntu's multiverse, where > the packaging requirements are lower? Could Hudson be considered a > binary non-free package, for the sake of reducing the work for us? I'd consider this very much a second-best solution - let's see how much work it really is, first. Thanks, -- Tim Retout <dioc...@debian.org> -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org