"Dr. Burkard Lutz" <b.l...@online.de> writes:

> there is no other upstream source except salsa.debian.org
> Is that sufficient?

Hi. This is certainly sufficient, but it raises more questions. These
tools weren't available to the public before this, I'm guessing, and
this is the initial public release?

Most programs in Debian (and every other distro) are separated into the
"upstream" part that contains the program being packaged, and the
"debianization": the packaging logic. While not strictly required, it
would be good to do that here as well. What if somebody finds these
tools, and wants to use them in some other distro? Hosting the sources
on salsa implies that there's something debian-specific in galvani, and
from reading the description, it sounds like there isn't.

So, unless you really feel strongly about doing it this way, I would
suggest that you

- Create a new "galvani" project someplace non-debian-specific (github,
  gitlab, etc...) with a README that tells people how to get the
  software. It can say "please use Debian and 'apt install galvani'" if
  that's what you want to communicate.

- Each release of "galvani" should have a git tag

- The repo on salsa should have the canonical structure used by most
  packages: an "upstream" branch containing the upstream sources from a
  release tarball and a "master" branch containing these sources + the
  debianization. One can debate about the technical pros/cons of doing
  this, but it's the standard, and will make it easier for you and
  others to manage this package.

Look at other packages for examples of how to structure this. You want
to have a debian/watch file that points to your repo; something like
this:

  https://salsa.debian.org/science-team/mrcal/-/blob/master/debian/watch

And you want to use the "uscan" program to read this file, to download
the sources. And you want to use the "gbp import-orig" tool to ingest
new tarballs.

Furthermore, I would encourage you to do this as part of a team. For
instance, the debian-science team:

  https://salsa.debian.org/science-team/

Doing this sends a signal that you are OK with other people helping
maintain this package. Their policies are described here:

  https://wiki.debian.org/Teams/DebianScience

I would suggest that you subscribe to their mailing list, and ask for
help there, if you need it. Or feel free to talk to me further on this
bug.

Reply via email to