Re: RFS: gen/0.4.0.1-1
On 29/06/2017 10:17, Andy Li wrote:
- I've created branches upstream and pristine-tar to better match
our gbp-based workflow
- I've added debian/gbp.conf
I've never used pristine-tar. Is it only for backing up the original
source tar file?
Sort of.
I only use `gbp import-orig path/to/upstream.tar.gz` when
creating/updating package. When I build it, I use debuild and
pbuilder-dist manually instead of `gbp buildpackage`.
I guess there is no need to change my workflow?
If you always keep the genuine .orig.tar.gz file in the parent of your
working directory, I think there is no need to change your workflow. But
if the file is missing (e.g. after a fresh `git clone`), `gbp
buildpackage` will recreate it. Otherwise, one would have to download
the .orig.tar.gz from somewhere (as I did, from mentors.debian.net).
`gbp buildpackage` is also useful for making tags for Debian releases (I
usually use it with --git-tag-only, though).
- Usually for team-maintained packages, "Maintainer" is set to
"Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org
<mailto:debian-ocaml-maint@lists.debian.org>>" and "Uploaders" is
set to whoever is in charge of the package. I let you think about it
and change that if you want.
I've just updated that as suggested, Uploaders is set to myself at the
moment.
Maybe the actual uploader (package sponsor) should be added to Uploaders
too?
I'm not sure who will that be though (Stéphane?).
There is no need for the sponsor or the occasional uploader to add
him/herself to Uploaders; any member of the team can make a so-called
"Team upload" if needed. The semantics of Uploaders (AFAIC) is the
actual maintainer of the package.
I will upload ocaml-gen soon. Thank you for your contribution.
Cheers,
--
Stéphane
Reply to: