Re: Survey: git packaging practices / repository format
- To: debian-devel@lists.debian.org
- Subject: Re: Survey: git packaging practices / repository format
- From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
- Date: Mon, 1 Jul 2019 15:00:47 +0200
- Message-id: <[🔎] 0f354915-f639-05f5-752b-d65fd5cab766@metux.net>
- In-reply-to: <259caba1ffb5ad20680acb59e2765b8f6d15b10f.camel@decadent.org.uk>
- References: <23789.22766.778482.983490@chiark.greenend.org.uk> <20190528173136.GB17513@espresso.pseudorandom.co.uk> <23789.38946.363651.512533@chiark.greenend.org.uk> <20190528233922.GA3018@espresso.pseudorandom.co.uk> <259caba1ffb5ad20680acb59e2765b8f6d15b10f.camel@decadent.org.uk>
On 29.05.19 15:14, Ben Hutchings wrote:
> Perhaps we should update policy to say that the .orig tarball may (or
> even "should") be generated from an upstream release tag where
> applicable.
ACK. But there should also be some definition or at least guideline on
what is considiered "applicable" (or better: when is it okay not doing
that) and some rules on how the generation process shall be done.
(maybe having some script with a defined name ?)
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
Reply to: