On Fri, Jan 06, 2023 at 11:01:19AM +0000, Ian Jackson wrote:
>...
> Adrian Bunk writes ("Bug#1028025: hippotat shouldn't be a native package"):
> > After reading the package description, nothing seems to make
> > this package native other than the main maintainer happening
> > to also be a DD.
> >
> > Please make the package non-native. There should be no downsides
> > in practice,
>
> I think the downsides is that I would end up splitting the release
> process in a confusing way, given that I intend to release upstream
> and to Debian simultaneously.
You build an orig.tar.xz without debian/ and then let dpkg generate
a source package with debian.tar.xz.
orig.tar.xz can be released as upstream sources.
I don't know what your workflow is, e.g. git-archive(1) with
export-ignore attribute for debian/ could be used to generate
the orig.tar.xz.
> > and it avoids weirdnesses like an NMU 1.1.3+nmu1 being
> > a new upstream version that other distributions like Yocto or Fedora
> > might integrate in their distribution as 1.1.3+nmu1-1.
>
> That would be fine ?
There are also other issues, like lack of patch management in the
package sources if someone else does a security or stable update
of your package. Which makes the changes harder to review for
other people.
All such issues are not fatal and also affect "real" native package
like dpkg or linitian, but this brings us back into the non-quilt
world of dpkg format 1.0 without the option of proper patch management.
Literally 99% of my uploads are NMU/stable/LTS uploads of packages other
people maintain, seeing changes from previous NMU/stable/LTS uploads
as series of patches helps me and being able to split my own changes
into separate patches makes it easier for other people to review my
changes.
> Ian.
cu
Adrian
