Re: Debian native package?
Chris Danis writes:
> I'm in the NM queue, currently packaging tclbabel, a piece of software
> I have written myself. Because I am both upstream and possibly Debian
> maintainer, should this be such a native package?
I don't like making for such packages native. I have one package that
I'm also upstream for, aewm. For practical purposes, I need the
.diff.gz to make the resulting .deb policy compliant (I patch the
Makefile and a compile-time option). Aesthetically, I just prefer
keeping the debian/ subdir organized with the corresponding stuff for my
other packages, away from development on the actual source.
You also have to consider what happens when you make an error in your
maintainer scripts, or need to fix a packaging-related bug that has
nothing to do with the non-Debian code. even if you haven't made any
changes that would affect users of other distributions, you'll still
have to bump the version number. So I'd go with the "written especially
for Debian" definition, although there can sometimes be exceptions.
--
things change.
decklin@red-bean.com
Reply to: