-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Russel Winder wrote:
> I would be delighted if this were a misconception. Given the above it
> seems that the following would be allowed by the Debian rules:
>
> 1. Build an instance of Gradle using a downloaded pre-compiled Gradle
> Wrapper.
> 2. Use the newly created compiled Gradle to compile Gradle to show that
> there is no dependence on a "binary blob" and create things that can be
> packaged . . .
> 3. Use this latterly created Gradle as input to the packaging process.
Yes, or rather:
1A. Build a Debian package using the wrapper or any binary Gradle
installation.
2A. Change the package to build with itself.
3A. Rebuild.
This is not very different from bootstrapping some compilers, though it can
be cumbersome at times (especially if repeated bootstrapping is needed for
each new version).
> Hans and/or Adam will almost certainly have to chip in here, but the
> problem I see is that the Gradle build specifies specific versions of
> the dependencies and these may be different from the instances of these
> dependencies in Debian at any given time.
That is a general problem for all Debian packages, we can handle it. We just
change the dependencies to use whatever version we have in Debian, and try
to make sure that it stays compatible. A good test suite helps a lot.
Cheers,
Marcus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkt6bAMACgkQXjXn6TzcAQlaUwCgv4osy6/0TBQZab6LSZzmF6df
goAAnAjgmljnSkiKEDBqGR+SCcLsf1Ji
=Q7jl
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
