Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #9712
| From | Jeremy Stanley <fungi@yuggoth.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: a few quick questions on gbp pq workflow |
| Date | 2017-08-06 21:20 +0200 |
| Message-ID | <ubzfI-6eX-3@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <ubwhP-4rV-7@gated-at.bofh.it> <ubwBc-4yy-21@gated-at.bofh.it> <ubytk-5JT-25@gated-at.bofh.it> <ubyWl-5Tz-17@gated-at.bofh.it> <ubz61-6bR-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On 2017-08-06 20:00:59 +0100 (+0100), Ghislain Vaillant wrote: [...] > You'd still have to clean the pre-built files, since they would be > overwritten by the build system and therefore dpkg-buildpackage > would complain if you run the build twice. > > So, you might as well just exclude them from the source straight > away, no? Repacking an upstream tarball just to avoid needing to tell dh_install not to copy files from a particular path into the binary package seems the wrong way around to me, but maybe I'm missing something which makes that particularly complicated? This comes up on debian-mentors all the time, and the general advice is to avoid repacking tarballs unless there's a policy violation or you can get substantial (like in the >50% range) reduction in size on especially huge upstream tarballs. Otherwise the ability to compare the upstream tarball from the source package to upstream release announcements/checksums/signatures is a pretty large benefit you're robbing from downstream recipients who might wish to take advantage it. -- Jeremy Stanley
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
a few quick questions on gbp pq workflow Allison Randal <allison@lohutok.net> - 2017-08-06 17:00 +0200
Re: a few quick questions on gbp pq workflow Jeremy Stanley <fungi@yuggoth.org> - 2017-08-06 18:10 +0200
Re: a few quick questions on gbp pq workflow Scott Kitterman <debian@kitterman.com> - 2017-08-06 18:30 +0200
Re: a few quick questions on gbp pq workflow Ondrej Novy <novy@ondrej.org> - 2017-08-06 20:30 +0200
Re: a few quick questions on gbp pq workflow Jeremy Stanley <fungi@yuggoth.org> - 2017-08-06 21:00 +0200
Re: a few quick questions on gbp pq workflow Ghislain Vaillant <ghisvail@gmail.com> - 2017-08-06 21:10 +0200
Re: a few quick questions on gbp pq workflow Jeremy Stanley <fungi@yuggoth.org> - 2017-08-06 21:20 +0200
Re: a few quick questions on gbp pq workflow Thomas Goirand <zigo@debian.org> - 2017-09-04 00:00 +0200
Re: a few quick questions on gbp pq workflow Ondrej Novy <novy@ondrej.org> - 2017-08-06 23:50 +0200
Re: a few quick questions on gbp pq workflow Jeremy Stanley <fungi@yuggoth.org> - 2017-08-07 00:30 +0200
Re: a few quick questions on gbp pq workflow Thomas Goirand <zigo@debian.org> - 2017-09-04 00:20 +0200
Re: a few quick questions on gbp pq workflow Scott Kitterman <debian@kitterman.com> - 2017-08-07 05:00 +0200
Re: a few quick questions on gbp pq workflow Paul Wise <pabs@debian.org> - 2017-08-07 16:50 +0200
Re: a few quick questions on gbp pq workflow Diane Trout <diane@ghic.org> - 2017-08-08 00:20 +0200
Re: a few quick questions on gbp pq workflow Scott Kitterman <debian@kitterman.com> - 2017-08-08 01:20 +0200
Re: a few quick questions on gbp pq workflow Scott Kitterman <debian@kitterman.com> - 2017-08-06 21:00 +0200
Re: a few quick questions on gbp pq workflow Ghislain Vaillant <ghisvail@gmail.com> - 2017-08-06 21:10 +0200
Re: a few quick questions on gbp pq workflow Barry Warsaw <barry@debian.org> - 2017-08-07 20:00 +0200
Re: a few quick questions on gbp pq workflow Thomas Goirand <zigo@debian.org> - 2017-09-04 00:00 +0200
Re: a few quick questions on gbp pq workflow Brian May <bam@debian.org> - 2017-08-07 01:10 +0200
csiph-web