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
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
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
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
> pack
I'm not aware of the implications but if it's just opinion you ask: dump
groovy 1. Groovy 2.x should build a lot of packages build with groovy 1.8.
Regards,
signature.asc
Description: OpenPGP digital signature
Le 2/02/2016 18:42, Ioan Eugen Stan a écrit :
> I'm not aware of the implications but if it's just opinion you ask: dump
> groovy 1. Groovy 2.x should build a lot of packages build with groovy 1.8.
Actually the transition to Groovy 2 is already done and Groovy 1.x will
go away in Stretch. The ques
6 matches
Mail list logo
