Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #9007 > unrolled thread
| Started by | chrysn <chrysn@fsfe.org> |
|---|---|
| First post | 2016-11-16 12:10 +0100 |
| Last post | 2016-11-16 23:00 +0100 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.debian.maint.python
policy question: tag format for patch-less packages chrysn <chrysn@fsfe.org> - 2016-11-16 12:10 +0100
Re: policy question: tag format for patch-less packages IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org> - 2016-11-16 22:00 +0100
Re: policy question: tag format for patch-less packages Scott Kitterman <debian@kitterman.com> - 2016-11-16 23:00 +0100
| From | chrysn <chrysn@fsfe.org> |
|---|---|
| Date | 2016-11-16 12:10 +0100 |
| Subject | policy question: tag format for patch-less packages |
| Message-ID | <sE6gh-21P-23@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hello team, I'm confused by the DPMT policy when it comes to git-dpm usage. On the one hand, git-dpm is introduced as the patch management regime. With what I understand of what git-dpm does, this means that it is not required or even useful when packages don't need patching. On the other hand, the tag format is defined in terms of git-dpm, even though the resulting tags seem to match what `gbp buildpackage --git-tag` produces. Should git-dpm be used even though no patches are present? Best regards chrysn -- To use raw power is to make yourself infinitely vulnerable to greater powers. -- Bene Gesserit axiom
[toc] | [next] | [standalone]
| From | IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org> |
|---|---|
| Date | 2016-11-16 22:00 +0100 |
| Message-ID | <sEftf-7M4-5@gated-at.bofh.it> |
| In reply to | #9007 |
[Multipart message — attachments visible in raw view] — view raw
On 11/16/2016 06:07 AM, chrysn wrote: > Should git-dpm be used even though no patches are present? how do you make sure that you will never need patches? (unless this is a native package) gfmards IOhannes
[toc] | [prev] | [next] | [standalone]
| From | Scott Kitterman <debian@kitterman.com> |
|---|---|
| Date | 2016-11-16 23:00 +0100 |
| Message-ID | <sEgpj-8pt-3@gated-at.bofh.it> |
| In reply to | #9008 |
On November 16, 2016 2:33:47 PM CST, "IOhannes m zmölnig (Debian/GNU)" <umlaeute@debian.org> wrote: >On 11/16/2016 06:07 AM, chrysn wrote: >> Should git-dpm be used even though no patches are present? > >how do you make sure that you will never need patches? (unless this is >a >native package) Also, git-dpm tag provides the needed tags regardless of if there is a patch. Regardless of patches, we still have an upstream branch and at least an unstable branch that need to be kept up to date. If someone else needs to add a patch to your package to resolve a bug, they shouldn't have to also check/redo the git archive configuration. All the team packages should use a common organization. Scott K
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web