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

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

Re: Groovy packaging

Show all headers | View raw

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

On Tue, 2016-02-02 at 18:11 +0100, Emmanuel Bourg wrote:
> 2. Reuse groovy to package the next version of Groovy 2.x and then
> remove groovy2 (we keep the 2.x artifact to avoid updating all the
> reverse dependencies)
> 
> 3. Turn groovy into a dummy package depending on groovy2. The groovy
> package would become the equivalent of default-jdk, always pointing
> to
> the latest version available.
> 

I like having the ability to install a package and have the latest
version available rather than remember that I'm using a specific API
version. The versioned api packages do have their uses though. I only
count a few packages that depend on groovy2 so it shouldn't take too
long for them to get updated.

Until we have a need for multiple groovy versions again, it's just
extra work to maintain and build a dummy package. Why not leave it
until its really needed?

I'd vote for (2).

Andrew

Back to linux.debian.maint.java | Previous | Next — Previous in thread | Next 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