Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #13565
| From | Sandro Tosi <morph@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: python-django-js-asset_1.2.2-3_source.changes REJECTED |
| Date | 2021-09-22 00:40 +0200 |
| Message-ID | <CZWAF-6Ec-7@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <CZaFH-2HO-7@gated-at.bofh.it> <CZceu-3Oh-23@gated-at.bofh.it> <CZpEJ-3D6-3@gated-at.bofh.it> <CZtfk-5SL-9@gated-at.bofh.it> <CZVbA-5Wb-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Sep 21, 2021 at 5:00 PM Antonio Terceiro <terceiro@debian.org> wrote: > > On Mon, Sep 20, 2021 at 11:14:44AM -0400, Sandro Tosi wrote: > > > That's because gbp does not use pristine-tar by default, and > > > debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to > > > fix that. > > > > I dont think this is the right approach: the default options to work > > on DPT packages should be in gbp default config file (or in another, > > global, config file), and not live in each and every package > > debian/gbp.conf file; it is already inconsistently maintained with > > several packages having uncommon settings that will take precedence > > over the default ones. > > I agree with you in theory; my global gbp.cons enables pristine-tar. > > However, having it duplicated in every package means we as a team work > consistently regardless of people's global configuration, not at all, right now we dont have a *consistent* debian/gbp.conf in each package, everyone writes their own and it's currently a mess. what when we decide to add a new option, or change the value of an existing one? DPT currently has ~2500 packages: how do you maintain consistency in all of them? > and that's one > less detail people need to get just right to be able to contribute > effectively. > > Also, one's global configuration might not apply to all the packages > they contribute to; it's easier for everyone if gbp just does the > right thing based on per-package configuration than expecting people to > remember to switch their defaults, or to pass options explicitly. please refer to https://lists.debian.org/debian-python/2021/09/msg00065.html for how i see this being implemented. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Antonio Terceiro <terceiro@debian.org> - 2021-09-19 21:30 +0200
Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Carsten Schoenert <c.schoenert@t-online.de> - 2021-09-19 23:10 +0200
Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Andrey Rahmatullin <wrar@debian.org> - 2021-09-20 09:30 +0200
Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Antonio Terceiro <terceiro@debian.org> - 2021-09-20 13:30 +0200
Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Sandro Tosi <morph@debian.org> - 2021-09-20 17:20 +0200
Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Andrey Rahmatullin <wrar@debian.org> - 2021-09-20 17:30 +0200
Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Sandro Tosi <morph@debian.org> - 2021-09-21 03:20 +0200
Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Thomas Goirand <zigo@debian.org> - 2021-09-20 21:50 +0200
Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Antonio Terceiro <terceiro@debian.org> - 2021-09-21 23:10 +0200
Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Sandro Tosi <morph@debian.org> - 2021-09-22 00:40 +0200
Re: writing debian/gbp.conf considered harmful [was: python-django-js-asset_1.2.2-3_source.changes REJECTED] Thomas Goirand <zigo@debian.org> - 2021-09-22 09:30 +0200
csiph-web