Orphaning some Java packages

2024-04-08 Thread Severin Gehwolf
Hi, I'm orphaning a couple of packages of mine which I no longer use or were used as a dependency of a package I've maintained before and am no longer using: Packages without co-maintainers: jolokia-jvm-agent prometheus-simpleclient-java prometheus-jmx-exporter P

Re: Orphaning some Java packages

2018-09-29 Thread Raphael Groner
> Gerald Henriksen wrote: > > > what rule is that? > > -- Rex Maybe our guidelines [*] about bundling and duplication is threatened with modularity. Last but not least, if there's a CVE or soname bump in whatever library, we'd need to rebuild the whole modularity stack depending. That would m

Re: Orphaning some Java packages

2018-09-28 Thread Israel Bermudez
I wouldn't use the word useless. Having the packages is just a quality of life thing. Just like for me as mainly C++ developer; not having Basel or abseil does not make Fedora useless for me or C++ developers. It doesn't take much effort to get your environment up and running script the procedur

Re: Orphaning some Java packages

2018-09-28 Thread Kevin Kofler
Mikolaj Izdebski wrote: > Users that want to reproduce Ant 1.10.2 build would need to repeat > series of builds and rely on information stored in Koji to know what > builds should be ran in what order. Trying to build packages only from > content released to users would be even more difficult. The

Re: Orphaning some Java packages

2018-09-28 Thread Nicolas Mailhot
Le vendredi 28 septembre 2018 à 10:26 -0400, Stephen John Smoogen a écrit : > On Fri, 28 Sep 2018 at 04:21, Nicolas Mailhot > wrote: > > Le vendredi 28 septembre 2018 à 10:09 +0200, Mikolaj Izdebski a > > écrit : > > > This is already not met for Fedora. Lets look at ant package which > > > you >

Re: Orphaning some Java packages

2018-09-28 Thread Stephen John Smoogen
On Fri, 28 Sep 2018 at 04:21, Nicolas Mailhot wrote: > > Le vendredi 28 septembre 2018 à 10:09 +0200, Mikolaj Izdebski a écrit : > > > > This is already not met for Fedora. Lets look at ant package which you > > mentioned earlier. > > > > That just shows it is urgent for Fedora to improve its hand

Re: Orphaning some Java packages

2018-09-28 Thread Rex Dieter
Gerald Henriksen wrote: > Fedora (rightly) > as a rule doesn't want multiple versions of libraries. what rule is that? -- Rex ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fe

Re: Orphaning some Java packages

2018-09-28 Thread Gerald Henriksen
On Fri, 28 Sep 2018 10:15:46 +0200, you wrote: >Le jeudi 27 septembre 2018 à 19:14 -0400, Gerald Henriksen a écrit : >> >> Or, short version, the Java ecosystem is either indifferent or hostile >> to distribution packages. > >Any language ecosystem is initially hostile to distribution packages.

Re: Orphaning some Java packages

2018-09-28 Thread Nicolas Mailhot
Le vendredi 28 septembre 2018 à 10:09 +0200, Mikolaj Izdebski a écrit : > > This is already not met for Fedora. Lets look at ant package which you > mentioned earlier. > That just shows it is urgent for Fedora to improve its handling of bootstrapping operations, because major languages depend on

Re: Orphaning some Java packages

2018-09-28 Thread Nicolas Mailhot
Le jeudi 27 septembre 2018 à 19:14 -0400, Gerald Henriksen a écrit : > > Or, short version, the Java ecosystem is either indifferent or hostile > to distribution packages. Any language ecosystem is initially hostile to distribution packages. Languages ecosystems are created by devs, that care l

Re: Orphaning some Java packages

2018-09-28 Thread Mikolaj Izdebski
On 09/28/2018 02:50 AM, Kevin Kofler wrote: > Mikolaj Izdebski wrote: >> Modules with their API specifications at least make it more clear what >> are expectations about packages. Something user may consider essential >> is only a build dependency for a packager and the packages won't receive >> en

Re: Orphaning some Java packages

2018-09-27 Thread Emmanuel Seyman
* Mikolaj Izdebski [24/09/2018 21:39] : > > Java SIG is dying slowly, this package set recently lost another > co-maintainer and I don't have time to maintain all these packages by > myself. Is there anyway to recruit new members? I've been told that Mageia's Java stack is a recompilation of Fedor

Re: Orphaning some Java packages

2018-09-27 Thread Kevin Kofler
Mikolaj Izdebski wrote: > Modules with their API specifications at least make it more clear what > are expectations about packages. Something user may consider essential > is only a build dependency for a packager and the packages won't receive > enough attention from the maintainer. As I wrote in

Re: Orphaning some Java packages

2018-09-27 Thread Gerald Henriksen
On Thu, 27 Sep 2018 10:34:33 -0400, you wrote: >On Mon, Sep 24, 2018 at 3:39 PM Mikolaj Izdebski wrote: >> >> Java SIG is dying slowly, this package set recently lost another >> co-maintainer and I don't have time to maintain all these packages by >> myself. Switching to module-only content is pr

Re: Orphaning some Java packages

2018-09-27 Thread Mikolaj Izdebski
On 09/26/2018 08:01 AM, Raphael Groner wrote: >>> Mikolaj Izdebski wrote: >>> >>> This is exactly what I feared when the modules were first proposed: >>> essential packages moving to modules only. >>> >>> I think this is absolutely a step in the wrong direction. Things like "ant" >>> are essentia

Re: Orphaning some Java packages

2018-09-27 Thread Mikolaj Izdebski
On 09/26/2018 04:17 AM, Kevin Kofler wrote: > Mikolaj Izdebski wrote: >> I'm in the process of transitioning maintenance of all software to >> modules only. The reason is that module maintenance is much easier >> compared to maintenance of non-modular, "ursine" packages. Starting from >> Fedora 29

Re: Orphaning some Java packages

2018-09-27 Thread Mikolaj Izdebski
On 09/24/2018 11:25 PM, Ben Rosser wrote: > On Mon, Sep 24, 2018 at 3:39 PM, Mikolaj Izdebski wrote: >> On 09/24/2018 08:52 PM, Miro Hrončok wrote: >>> On 24.9.2018 19:09, Mikolaj Izdebski wrote: I'm in the process of transitioning maintenance of all software to modules only. The reason

Re: Orphaning some Java packages

2018-09-27 Thread Mikolaj Izdebski
On 09/27/2018 04:34 PM, Neal Gompa wrote: > On Mon, Sep 24, 2018 at 3:39 PM Mikolaj Izdebski wrote: >> >> Java SIG is dying slowly, this package set recently lost another >> co-maintainer and I don't have time to maintain all these packages by >> myself. Switching to module-only content is probabl

Re: Orphaning some Java packages

2018-09-27 Thread Mikolaj Izdebski
On 09/24/2018 08:32 PM, Christopher wrote: > I have a question about this because I don't fully understand modularity. > If these packages are retired, how will maintainers get them installed from > their respective modules in order to build their own packages, and how will > users get the appropri

Re: Orphaning some Java packages

2018-09-27 Thread Neal Gompa
On Mon, Sep 24, 2018 at 3:39 PM Mikolaj Izdebski wrote: > > Java SIG is dying slowly, this package set recently lost another > co-maintainer and I don't have time to maintain all these packages by > myself. Switching to module-only content is probably the best move to > keep high-quality software

Re: Orphaning some Java packages

2018-09-27 Thread Christopher
I have a question about this because I don't fully understand modularity. If these packages are retired, how will maintainers get them installed from their respective modules in order to build their own packages, and how will users get the appropriate modules installed to satisfy dependencies? Or i

Re: Orphaning some Java packages

2018-09-27 Thread Miro Hrončok
On 24.9.2018 19:09, Mikolaj Izdebski wrote: I'm in the process of transitioning maintenance of all software to modules only. The reason is that module maintenance is much easier compared to maintenance of non-modular, "ursine" packages. Ideally these packages should be retired instead of orphani

Re: Orphaning some Java packages

2018-09-25 Thread Raphael Groner
>> Mikolaj Izdebski wrote: >> >> This is exactly what I feared when the modules were first proposed: >> essential packages moving to modules only. >> >> I think this is absolutely a step in the wrong direction. Things like "ant" >> are essential parts of a distribution. They cannot sit in some

Re: Orphaning some Java packages

2018-09-25 Thread Kevin Kofler
Mikolaj Izdebski wrote: > I'm in the process of transitioning maintenance of all software to > modules only. The reason is that module maintenance is much easier > compared to maintenance of non-modular, "ursine" packages. Starting from > Fedora 29 modules are first-class citizens, so I am finally

Re: Orphaning some Java packages

2018-09-24 Thread Ben Rosser
On Mon, Sep 24, 2018 at 3:39 PM, Mikolaj Izdebski wrote: > On 09/24/2018 08:52 PM, Miro Hrončok wrote: >> On 24.9.2018 19:09, Mikolaj Izdebski wrote: >>> I'm in the process of transitioning maintenance of all software to >>> modules only. The reason is that module maintenance is much easier >>> co

Re: Orphaning some Java packages

2018-09-24 Thread Mikolaj Izdebski
On 09/24/2018 08:52 PM, Miro Hrončok wrote: > On 24.9.2018 19:09, Mikolaj Izdebski wrote: >> I'm in the process of transitioning maintenance of all software to >> modules only. The reason is that module maintenance is much easier >> compared to maintenance of non-modular, "ursine" packages. >> >> I

Orphaning some Java packages

2018-09-24 Thread Mikolaj Izdebski
TL;DR I am planning to orphan Java packages listed below soon after Fedora 29 GA. Let me know if you want to adopt any of them. I'm in the process of transitioning maintenance of all software to modules only. The reason is that module maintenance is much easier compared to maintenance of non-modu

Orphaning some Java packages

2018-01-02 Thread Jerry James
I have orphaned some Java packages. These two were used to support jnormaliz, which used to be part of the normaliz package. It is now a separate project, and I don't use it, so I am not packaging it. If somebody would like to do so, you will want to take up these two packages: - balloontip (bal