Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #8825

Re: Groovy packaging

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Am 03.02.2016 um 17:27 schrieb Emmanuel Bourg:
> Le 3/02/2016 13:53, Markus Koschany a écrit :
> 
>> I like having one source package src:groovy that always provides the
>> latest upstream release and all its reverse-dependencies shall always
>> work flawlessly with it. Amen. :-)
> 
> +1
> 
> The user experience is important to me, and I think 'apt-get install
> groovy' is more intuitive than 'apt-get install
> groovy<guessthelatestversionavailable>'. But it doesn't mean the groovy
> package has to be built from src:groovy.

True. Though src:groovy already contains the binary package of the same
name, which is why the package doesn't have to go through NEW.


>> So I would prefer to package the next version of groovy 2.x
>> in src:groovy and to remove src:groovy2. I can see the benefits of
>> option number three but it should be limited to packages where we also
>> provide an alternative like switching between two different JDKs and
>> when many, if not all Java packages, are affected by this choice.
> 
> I also thought the option 2 was a good idea, and as I updated groovy2 to
> the latest version yesterday I hesitated to do it. I wasn't sure about
> the upgrades and the backports:
> - We probably want the Jessie users of the groovy and groovy2 packages
> to end up automatically with the latest Groovy 2.x when upgrading to
> Stretch. This means we have to keep a groovy2 binary package (either
> with the full runtime or just a dummy dependency package).
> - Backporting groovy2 to Jessie might be more complicated if we switch
> back to src:groovy. It isn't just a rebuild, we have to rename the
> binary packages and change the paths too.

I haven't thought too much about backports yet because we could also
keep the old src:groovy2 package until the freeze for Stretch starts, if
this helps to ease backports. But with the release of Stretch
src:groovy2 should have been removed. So let's package the next release
of groovy in src:groovy, switch all r-deps back to groovy and return to
debian artifacts. This could all be adjusted with the next upload and
hey there are only 25 r-deps. If we split the work it shouldn't take
that long.

Markus

Back to linux.debian.maint.java | Previous | Next — Previous in thread | Find similar

Thread

Groovy packaging Emmanuel Bourg <ebourg@apache.org> - 2016-02-02 18:20 +0100
  Re: Groovy packaging Ioan Eugen Stan <stan.ieugen@gmail.com> - 2016-02-02 18:50 +0100
    Re: Groovy packaging Emmanuel Bourg <ebourg@apache.org> - 2016-02-02 19:30 +0100
  Re: Groovy packaging Andrew Schurman <arcticwaters@gmail.com> - 2016-02-03 02:30 +0100
  Re: Groovy packaging Markus Koschany <apo@debian.org> - 2016-02-03 14:00 +0100
    Re: Groovy packaging Emmanuel Bourg <ebourg@apache.org> - 2016-02-03 17:30 +0100
      Re: Groovy packaging Markus Koschany <apo@debian.org> - 2016-02-04 00:30 +0100

csiph-web