Re: Getting Maven Into Main - What Next?

[Paul Cager <paul-debian@home.paulcager.org>]

Florian Weimer wrote:
> * Paul Cager:
> 
>> Now that we are making progress with packaging Maven's
>> Build-Dependencies, I'm beginning to wonder what happens next. I've
>> noticed from the JavaCC packaging that it seems to be all right to
>> include a "bootstrap jar" in the upstream source. Is this right? I guess
>> to be valid:
>>
>>    * When building the package a new Jar must be built (from source)
>>      that could replace the bootstrap Jar.
> 
> This is a bit tricky.  Theoretically, you are supposed to bootstrap
> from an installed version (IOW, a self-depdency).  However, several
> packages (Ocaml, for instance) bootstrap from blobs.  In case of
> source code generators, it's also common to ship the processed source
> files.

Thinking about it, am I worrying unnecessarily here?  The source
downloaded from svn *does* include Jars, but I think these are only used
to run the unit tests. (I'm guessing; Trygve could you confirm this,
please?).

Once we have the build-dependencies packaged we should be able to
download the svn source, delete the jars and create an upstream source
tarball. Then debian/rules could just call the bootstrap.sh script
(possibly amended to prevent net access).

I don't think my brain is working this week...