Hi, So if my understanding is right, Jenkins is highly likely to be removed from Debian. And the reason behind this is because the release cycle of Jenkins is way too short and upstream already provides .deb?
So this makes me think about what exactly should be packaged into Debian. There are not too many softwares providing .deb distributions in upstream, but what if some of the softwares whose packages are already in Debian starts to provide upstream .deb, will we still have the motivation to keep maintaining it? For example, Gradle does not have .deb in upstream, but SBT does, and Gradle indirectly depends on SBT, then should we package SBT into Debian as well, which even though means lots of work? So what if there are some new packages that depends on libraries of Jenkins and someone wants to package it, what should he do? By the way, I am not using Jenkins in daily life, I am simply curious. :) Regards, Kai-Chung Yan 2016-01-21 0:41 GMT+08:00 Emmanuel Bourg <ebo...@apache.org>: > Le 14/01/2016 10:15, Thorsten Glaser a écrit : > >> Hrm, so is upstream’s packaging any good then? I have seen >> so many attempts of upstream to package “for” Debian that >> I don’t believe them unseen any more… > > Reproducibility put aside the upstream package is quite good. The > dependencies and the paths used are correct. It even managed to upgrade > my years old installation of Hudson and turn it into a shiny and up to > date instance of Jenkins without losing anything. > > >> … (plus I’d not know which version to pick, and “nobody >> ever got fired for buying IB^W^Wusing what’s in Debian” ☺) > > That's probably true for the upstream jenkins package too ;) > > Emmanuel Bourg > -- /* * 殷啟聰 | Kai-Chung Yan * 一生只向真理與妻子低頭 * Full-time student of National Taichung University of Education * LinkedIn: <https://linkedin.com/in/seamlik> * Blog: <seamlik.logdown.com> */
