Discussion thread

[cdluminate]

This issue is for generic discussion. Discussions following the original post should be redirected here.

[paddatrapper]

I've been playing around with this, trying to package a mostly simple piece of software I develop (top30). I was using the folded format. My main suggestions are:

• Allow addition of debhelper add-ons without needing to overwrite the default rules template
• Allow the addition of extra fields in debian/control without needing to overwrite the default control template (or allow variable substitution in the overridden template. For example packaging python applications requires X-Python3-Version field for limiting python3 versions.
• Use 3.0 (quilt) as the source format by default (and the required revision number in the changelog) so that patches are supported easily.

I do like the ease that this gives packaging. Although it was still slow going for me (admittedly much was around getting debhelper to properly use python3...), even having packaged many applications for Debian in the past. At the moment it feels like any complex packaging required by applications is going to be difficult to do here, but then it is difficult the usual way too, so I don't think that is indicative of any issues with DUPR, but rather just that the package is complex.

[cdluminate]

@paddatrapper Thank you for the feedbacks. I have added new issues for the suggestions, please check the issue list. Some of them will be fixed in the next release, including the dh addon support.
I'd also like to explore some more complicated examples, and see whether we can do something for those complicated ones.

Apart from that, X-Python3-Version is actually a deprecated feature in Debian 10 and sid.

[cdluminate]

@paddatrapper v0.0d had been released, along with some updates according to your feedbacks. Does it look better now?

[paddatrapper]

@cdluminate when packaging python3 only applications, specifying dh_with=python3, will result in build depends being added for python-all,python-all-dev, which makes pybuild try build the package for Python 2.7 (which obviously fails). The build deps should probably be more granular with the python3 deps added for dh_with=python3 and python deps added for dh_with=python. I guess the issue is how to handle dh_python, which is required for both and should only be listed once for applications that support both python 2 and 3.

[cdluminate]

@paddatrapper See #45