using existing workflows?
In working with the ImageMagick package, I noticed that the maintainer
uses gitpkg's debian/source/git-patches system to factor in upstream
patches in Debian. We haven't used this so far in the wheezy upload so I
kept working that way, especially since i'm not very familiar with that
system. I do wonder, however, if we should respect existing systems like
this, especially in the case (like here) where the package is under
collab-maint.
Are we expected to learn the package-specific workflows like those when
maintaining packages in LTS?
I had a similar situation with the Nagios3 package where I lost precious
time re-learning dpatch, to my horror. I wonder if it wouldn't have been
simpler to just convert that thing to quilt, especially since the
maintainer did exactly that in jessie. Since the previous LTS upload
kept using dpatch, I plowed on with a horrible hack (yay: rm in a dpatch
script!), but I did wonder if i would have saved time just doing the
conversion.
We often stumble upon a surprising variety of software out there. While
I can grok a lot of programming languages and toolchains, one has to
wonder how many of those we can efficiently keep in our heads at
once. :)
A.
--
The university must paint itself black, mulatto, worker anddd
peasant. If not, people will break down their doors and paint the
university the color they like.
- Ernesto "Che" Guevara
Reply to: