Re: Policy 3.8.0 and README.source
* Ansgar Burchardt <ansgar@2008.43-1.org> [2008-06-09 17:45:31 CEST]:
> Gerfried Fuchs wrote:
> > ... and that's why I am writing this mail. We propably want to define
> > at least team internal some default snippets/text for that, depending on
> > wether which patch tool our packages are using, and if a new upstream
> > tarball needs special tweaking.
>
> Won't the new source package format "3.0 (quilt)" make this unnecessary
> for most of our packages? It would apply the patches directly when the
> source is extracted, so no further explanations are needed.
Erm, not really. Further explenations _are_ needed, about how to add a
new patch to such a source package. But I would expect something similar
to /usr/share/doc/quilt/README.source will get added to dpkg itself
(README.quilt or such?). It's not done yet, so we can't reference that.
> The announcement for the updated policy [1] says that it's not a
> priority to adjust packages for lenny, and the new source package should
> be allowed in lenny+1.
The new source package format doesn't solve the problem, it just makes
it even more needed.
Just for a reference, this is what I currently use in wesnoth:
#v+
$ cat debian/README.source
This package uses quilt for its patch management, see
/usr/share/doc/quilt/README.source if you are unfamiliar with it.
Upstream ships their tarballs as .tar.bz2 files - which the Debian pool
unfortunately doesn't like (yet). All I do with them is piping them
through bzcat and gzip, like this for e.g. the 1.4.3 release:
bzcat wesnoth-1.4.3.tar.bz2 | gzip --best -c > wesnoth_1.4.3.orig.tar.gz
#v-
It is quite terse and it might fulfill the policy, but personally I'm
not totally happy with it.
So long,
Rhonda
Reply to: