[git-buildpackage] A basic question to begin

[Seamus de Mora]

I should state this again for clarity:
My objective is to create a git repo that allows users to clone, and
then successfully
build a .deb package for 'dhcpcd5' without recourse to an
"external" tarball. By "external" I only mean that all of the data needed to
successfully complete the build process is contained within the cloned git
repo.

> The pristine-tar manpage has example:
>
>   https://manpages.debian.org/bullseye/pristine-tar/pristine-tar.1.en.html



   1. Re the example: I don't know what a "forge" site is... as in
   'sourceforge'?
   2. Reading this manpage, this passage from the Description seems to
   answer my question re the 'upstream' branch that was imported, assuming
   that 'gbp import-dsc' does what's described as "typical" below:

"pristine-tar can regenerate an exact copy of a pristine upstream tarball
using only a small binary *delta* file and the contents of the tarball,
which are typically kept in an *upstream* branch in version control"


FWIW: Under the 'Options' heading, the text used for the option
listings is buggered.
It appears to be some sort of over-printing - don't know how to describe
this, so I've attached a screenshot here that shows it clearly.

[image: Screen Shot 2022-05-07 at 2.17.56 PM.png]
>
> and the Debian Wiki:
>
>   https://wiki.debian.org/DebianPackaging--pristine-tar-option-explained

I'm sorry, the explanation in this wiki does not help me much. I did learn
that Debian has been unable to reconcile the old way with the new way -
which was a bit of a surprise since git has been around for a while now.
But it's not been part of my objective to take on any "tarball baggage". I
hope to deal with it one time during the import, and be done with it.
However, if someone else wants or needs a '*.orig.tar.xz', I would like to
make sure my repo has the ingredients they need to re-create it.

And so, it appears the answer to my earlier questions is this:

*Use the `pristine-tar' option with '**gbp import-dsc' when importing a
conventional package into git. Using this option will provide users and
maintainers the option to re-create the pristine tarball (**'*.orig.tar.xz'*
*)** if needed.*

Does that sound about right???
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sigxcpu.org/pipermail/git-buildpackage/attachments/20220507/76b01e95/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2022-05-07 at 2.17.56 PM.png
Type: image/png
Size: 12899 bytes
Desc: not available
URL: <http://lists.sigxcpu.org/pipermail/git-buildpackage/attachments/20220507/76b01e95/attachment-0001.png>