Peter Krefting wrote: > How does this interact with the actual Git repository, when it comes > to detecting patches to upstream and such? I haven't really read up > on how the format is specified, so please point me in that direction > if what I am asking is obvious. It *is* the actual git repository, in basically all respects. > I have some software packaged for Debian, and I usually have the > upstream master branch as master, and a debian branch with Debian > changes (merging the upstream release as they come). Or, if the > upstream source is not in Git already, a branch of imported > tarballs. Or, when I am the upstream, I have everything (including > the debianization) on the master branch. > > When I want to package such software, do I just clone the repository > on the correct commit and have dpkg handle it? Does it still need > the upstream tarball, or will the entire source be reconstructed > from the git archive? You checkout the debian branch or whatever branch you have the debianization on, and build the package from there. (You may use pristine-tar to store the upstream tarball in the git repo if desired, but this is not strictly necessary.) -- see shy jo
Attachment:
signature.asc
Description: Digital signature