Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod
From: Emmanuel Bourg <ebourg@apache.org>
Newsgroups: linux.debian.maint.java
Subject: Re: gradle reboot
Date: Fri, 29 Nov 2024 13:00:01 +0100
Message-ID: <JO7Pb-csQd-7@gated-at.bofh.it>
References: <JJqpr-9klD-5@gated-at.bofh.it> <JN3DX-bLiV-1@gated-at.bofh.it> <JO6Jr-crX8-5@gated-at.bofh.it> <JO7Fv-csK8-5@gated-at.bofh.it>
Old-Return-Path: <ebourg@apache.org>
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Approved: robomod@news.nic.it
Lines: 30
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:12840

Le 29/11/2024 à 12:40, sre4ever@free.fr a écrit :

> Or maybe we can keep all of them in experimental for a while, and 
> duplicate only those that prove (or are suspected eventually, after 
> discussing that) to be problematic? I would rather keep things as 
> straightforward as possible with the dependencies, gradle has a lot of 
> dependencies but several of them only have very few reverse-dependencies 
> other than gradle and sometimes kotlin.

I'm not a big fan of potentially long lived experimental packages as it 
makes updates in sid more complicated. For example let's say the package 
foo has the version 1.0 in sid/testing and the version 3.0 in 
experimental, the upstream and pristine-tar branch on salsa are updated 
to the 3.0 release. If I want to update the sid package to 2.0, I can't 
import the release without rebasing/reimporting the experimental 3.0 
release on these branches.


> By the way, any opinion about making that new gradle a "gradle8" package 
> that provides "gradle"? My feeling is that maintaining up to 3 major 
> versions of Gradle is probably going to be necessary, given the breaking 
> changes with every major release (and sometimes in between) and what's 
> already announced for future releases.

I have no objection to upload even 10 versions of Gradle if that's part 
of a plan to get to the latest release and eventually drop the temporary 
packages. We can keep the extra releases in sid only to avoid raising 
concerns from the release and security teams.

Emmanuel Bourg