Re: Groovy packaging

2016-02-03 Thread Markus Koschany
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 u

Re: Handle sbt dependencies

2016-02-03 Thread Fabio
Hi Emmanuel, Il 02/02/2016 09:02, Emmanuel Bourg ha scritto: > I don't think there is an up to date tutorial. Studying existing > packages is the best source of inspiration. And we'll be happy to guide > you on this list or on IRC. > > Emmanuel Bourg Thanks a lot for your answers and for your sup

Re: Groovy packaging

2016-02-03 Thread 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 instal

Re: Groovy packaging

2016-02-03 Thread Markus Koschany
Hi, Am 02.02.2016 um 18:11 schrieb Emmanuel Bourg: > Hi all, > > Jenkins is going to be removed, this is the last dependency on the > groovy package. This opens the question of the groovy and groovy2 > packages. Should we: > > 1. Remove groovy and keep only groovy2. We may later reuse groovy for