Re: a few quick questions on gbp pq workflow
On August 6, 2017 2:11:13 PM EDT, Ondrej Novy <novy@ondrej.org> wrote:
>Hi,
>
>2017-08-06 12:26 GMT-04:00 Scott Kitterman <debian@kitterman.com>:
>>
>> I don't work on the OpenStack packages, but I do maintain a
>reasonable
>> number of Python packages. I always work from the released tarball.
>I
>> haven't added the keys yet to verify all my packages, but am
>gradually
>> doing so as I have time.
>>
>> I know some people like working from the upstream git (and the team
>> maintenance workflow allows for either), but I definitely prefer
>working
>> from the upstream tarballs and appreciate the effort that goes into
>> producing them.
>>
>
>It's not always possible/simple/nice to use sdist, because it contains
>prebuild docs. And I don't like to do +dfsg rebuild just for removing
>docs.
>Sometimes sdists doesn't contain tests.
>
>So my preference is:
>
> - use sdist if it's possible (have tests, don't have prebuilds, ...)
> - use git tag tarballs (https://github.com/<group>/<projects>/tags)
>
>I already migrated few packages OS->DPMT so far.
Great.
Generally when I find shortcomings in the tarball, I file bugs upstream. In general, I've found upstream developers to be accepting of such changes.
There's no need to DFSG the tarball if you can rebuild the docs. The best way to ensure that is to rebuild them during the build process.
Scott K
Reply to: