On 2017-07-05, Michael Mrozek wrote:
Am Tue, 4 Jul 2017 09:11:44 +0200 hat Sébastien Huss sebastien.huss@gmail.com geschrieben:
Do we need one GIT for each debian package we build and provide? (for example, meta-packages, our own config setups and daemons, the gl-wrapper, etc.) or can that be handled with one GIT where we have subdirectories for the packages?
That's how debian is working, see : https://anonscm.debian.org/cgit I'm guessing that's the way to go.
Ah - I'm not quite sure yet... is that one git with subdirectories? It more looks like a main git with links to various other gits...?
That's all the git repositories hosted on debian's git infrastructure (some may be hosted elsewhere).
In Debian, typically there is one VCS repository for each source package (there are exceptions, as each package maintainer can decide their own workflow, or the limitations of other VCSes used). A source package may contain several binary packages (e.g. linux source builds linux-image-*, linux-base, linux-headers-*, linux-doc-*, etc.).
I'd recommend sticking with one git repository for each source package, at least for things building actual .deb files. In many cases, you may be able to simply merge Debian's git branch for a given package, which makes it easier to merge in future changes (e.g. security updates). Although there are tools such as "gbp import-dscs" that can make merging work as well, if the package maintainer in Debian isn't consistant with your preferred workflow.
Hopefully there won't be a lot of divergence from Debian, which should make life a lot simpler all around... :)
Anyone who wants to help (and can help) aTc here?
I've mostly just been lurking lately, but could probably help a bit. I've got many years of Debian packaging experience working within Debian, although there are some types of packages I tend to keep at a safe distance.
live well, vagrant