I made a single file in ShellScript. To walk to Debian inclusion, somebody suggested me to publish it in a control version system (as Git). I've deployed this GitLab instance and now I only want to sure this is packageable. At this point, I prefer a single branch (master?) if it's possible, to use an easy tool (if it's possible) that makes Debian packages from this very simple source.
I've chosen git-buildpackage only because it seemed a simple tool to package from online sources. I leave sophistications and "pro" deployments for the future, to not become crazy today. __________ I'm using this express-made address because personal addresses aren't masked enough at lists.debian.org archives. El 20/12/16 a les 13:21, Andrey Rahmatullin ha escrit: > On Tue, Dec 20, 2016 at 12:57:21PM +0100, Narcis Garcia wrote: >> Maintaining debian-branch, upstream-branch and pristine-tar... Does it >> mean that I'll need to replicate "master" branch to those 3 sub-branches >> each time I wan to apply an update? > Working with the upstream git repo is covered at > file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.UPSTREAM.GIT.NOTARBALL > You have the upstream code in the upstream branch and the upstream+debian > code in the master branch and you use the upstream tags. > >> Same for each upstream/<release> subdirectories? > Those are not subdirs but tags, and if you use the upstream repo directly > you should use the upstream tags directly, by configuring gbp. > > > Note that it will be much harder for you to learn the workflows when > working with just one repo for your code and your packaging. Usual > workflows assume that you are not the author of the code you are > packaging. >
