On Tue, 19 Oct 2010, Christine Spang wrote: > > but on a sidenote -- since upstream is also under git, consider in > > future for your debian packaging just rely not on 'source distribution > > >...< > Sure, you make a good point. Do you know of any resources in > particular about workflows for having managing > upstream+debian both in git? A pointer might help me get on > this faster.
For ideal workflow for all scenarios, git-buildpackage still needs to be 'adjusted' a bit. We are discussing possible extensions for git-buildpackage author atm. But, it is already very convenient, especially if you do not need any DFSGing of upstream sources, then just keep your master -- upstream development, create debian branch on top of it with your packaging, provide debian/gbp.conf which would say that you have those two branches (e.g. see http://github.com/neurodebian/psychopy/blob/debian/debian/gbp.conf for an example), and then just do git-buildpackage --git-tag ;-) that would perform out of tree build and tag your debian release. Guido had a good talk at debconf10 about git-buildpackage. Although it is primarily tuned for packaging based on tarballs, it gives good overview of git-buildpackage functionality. so, for now it would just require your manual interaction for fetching, progressing master and merging it into debian, and invoking git-buildpackage. -- .-. =------------------------------ /v\ ----------------------------= Keep in touch // \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User ^^-^^ [175555] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
