If I wanted to follow the pattern of:
https://salsa.debian.org/pkg-voip-team/libosip2 https://salsa.debian.org/vagrant/librecast (my friends project)
Sorry, it's just small overview, how I do it.
Why would it be useful on that page?Sorry, it's just small overview, how I do it.
Brilliant, thank you Juri! Did you add this to the UpstreamGuide wiki at all?
https://salsa.debian.org/pkg-voip-team/libosip2 https://salsa.debian.org/vagrant/librecast (my friends project)These use two different workflows.
libosip2 uses gbp and gbp-import-orig, importing upstream tarballs.
librecast adds the upstream repo as a remote and merges upstream tags directly. It's not clear if it implies using gbp as there is no gbp.conf
that would set the correct upstream tag pattern.
How best do I start?Thre are many different workflows and you need to choose one. If you
decide to use gbp you can read https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.upstream-git.html
for some of the possible ones. I think gbp-import-orig+pristine-tar is the most popular among those.
I was asking why would it be useful on the UpstreamGuide page which is explicitly for upstreams, not packagers.Brilliant, thank you Juri! Did you add this to the UpstreamGuide wiki at all?Why would it be useful on that page?
For me it was like the difference between reading a computer science
book and source code. Juri's examples clearly showed the practical
steps of the workflow.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (1 / 15) |
Uptime: | 160:22:47 |
Calls: | 10,385 |
Calls today: | 2 |
Files: | 14,056 |
Messages: | 6,416,492 |