Re: Difficult Packaging Practices

2019-05-28 Thread Niels Thykier
Vincent Bernat: > ❦ 28 mai 2019 06:30 +00, Niels Thykier : > >> I.e. with the proper implementation of "make-it-work" (in the lack of a >> better name - maybe something "fetch-and-build"), the following should >> be possible >> >> """ >> #!/usr/bin/make -f >> >> # DISTRIBUTION = $(shell sed -n

Simplified Debianization Process (was: Re: Difficult Packaging Practices (OT)

2019-05-28 Thread Mo Zhou
Hi Thomas, On 2019-05-28 07:48, Thomas Dettbarn wrote: > Debian was quite more complicated, and the documentation on that > topic was scattered all over the interwebs. Here I had to download > the sources, rename the directories, rename the package, repackage, > change some files, count the

Re: Difficult Packaging Practices (OT)

2019-05-28 Thread Alex Mestiashvili
On 5/28/19 9:48 AM, Thomas Dettbarn wrote: > Hello. > > > This is slightly off-topic, and I have not been on this mailinglist > since this thread started. Nevertheless, I would like to express my > support for changing the packaging practices. > > Over the last two weeks, I tried creating ports

Re: Difficult Packaging Practices (OT)

2019-05-28 Thread Thomas Dettbarn
Hello. This is slightly off-topic, and I have not been on this mailinglist since this thread started. Nevertheless, I would like to express my support for changing the packaging practices. Over the last two weeks, I tried creating ports and packages for my project "dMagnetic". It was rather

Re: Difficult Packaging Practices

2019-05-28 Thread Vincent Bernat
❦ 28 mai 2019 06:50 +00, PICCA Frederic-Emmanuel : >> packages. While my Perl is a bit rusty, I can propose some "dh_fetch" >> helper for this if there is no huge opposition against this approach. > > why not a dh_uscan ? > > what is the fundamental difference between dh_fetch and what you can

Re: Difficult Packaging Practices

2019-05-28 Thread Vincent Bernat
❦ 28 mai 2019 06:30 +00, Niels Thykier : > I.e. with the proper implementation of "make-it-work" (in the lack of a > better name - maybe something "fetch-and-build"), the following should > be possible > > """ > #!/usr/bin/make -f > > # DISTRIBUTION = $(shell sed -n "s/^VERSION_CODENAME=//p"

Re: Difficult Packaging Practices

2019-05-28 Thread Niels Thykier
Vincent Bernat: > ❦ 28 mai 2019 08:59 +08, Paul Wise : > >>> People using tools like fpm will never get familiar with our tools and >>> will never be contributors. >> >> I enjoyed your blog post about pragmatic packaging using Debian's >> tools instead of fpm, it seems like a good approach if

Re: Difficult Packaging Practices

2019-05-27 Thread Vincent Bernat
❦ 28 mai 2019 08:59 +08, Paul Wise : >> People using tools like fpm will never get familiar with our tools and >> will never be contributors. > > I enjoyed your blog post about pragmatic packaging using Debian's > tools instead of fpm, it seems like a good approach if one is > committed to using

Re: Difficult Packaging Practices

2019-05-27 Thread Paul Wise
On Mon, May 27, 2019 at 2:52 PM Vincent Bernat wrote: > People using tools like fpm will never get familiar with our tools and > will never be contributors. I enjoyed your blog post about pragmatic packaging using Debian's tools instead of fpm, it seems like a good approach if one is committed

Re: Difficult Packaging Practices

2019-05-27 Thread Sam Hartman
> "Ben" == Ben Finney writes: Ben> Sam Hartman writes: >> If you just want to get upstream's idea of their package onto a >> system with their release schedule and their recommended >> dependency versions, there are better ways than getting a package >> into Debian.

Re: Difficult Packaging Practices

2019-05-27 Thread Sam Hartman
> "Russ" == Russ Allbery writes: Russ> This is my experience as well. I've occasionally tried to get Russ> people at work (at various jobs) interested in packaging Russ> software for Debian, without all that much success. The Russ> problem seems less any one specific thing

Re: Difficult Packaging Practices

2019-05-27 Thread Vincent Bernat
❦ 27 mai 2019 16:15 +10, Ben Finney : >> If you just want to get upstream's idea of their package onto a system >> with their release schedule and their recommended dependency versions, >> there are better ways than getting a package into Debian. > > In the Debian mentors forum (that is, the

Re: Difficult Packaging Practices

2019-05-27 Thread Ben Finney
Sam Hartman writes: > If you just want to get upstream's idea of their package onto a system > with their release schedule and their recommended dependency versions, > there are better ways than getting a package into Debian. In the Debian mentors forum (that is, the chat channel, the mailing

Re: Difficult Packaging Practices

2019-05-26 Thread Russ Allbery
Sam Hartman writes: > I think it's a combination of a lot of things. We have high standards, > a lot of complexity, and you have to get most or all of that right to > contribute. You have to have a package that meets our standards. You > have to have a copyright file that meets our standards.

Re: Difficult Packaging Practices

2019-05-26 Thread Jérémy Lal
Le dim. 26 mai 2019 à 23:01, Sam Hartman a écrit : > > "Adrian" == Adrian Bunk writes: > > Adrian> It is a problem for people making their first contributions > Adrian> to Debian to get them into unstable. The problem here is > Adrian> lack of sponsors willing to do proper