[Pkg-osm-maint] Bug#678426: Bug#678426: libjs-leaflet: should mention stripped source in copyright (or use pristine source)

Jonas Smedegaard dr at jones.dk
Mon Jun 25 23:52:37 UTC 2012


On 12-06-22 at 07:44pm, Andrew Harvey wrote:
> On 22/06/12 02:48, Jonas Smedegaard wrote:
> > Debian Policy requires (or only recommends? I don't recall) that if 
> > upstream source is not redistributed as-is then mangling be 
> > documented in debian/copyright.
> > 
> > Seems from the CDBS hints that libjs-leaflet strips upstream 
> > generated JavaScript files.
> > 
> > Either this should be documented, or preferrably - as the stripping 
> > seems unnecessary to me - the source should be used as-is, but those 
> > files instead be put aside when building the files used for binary 
> > packaging.
> 
> While it is hard to argue this case, in general by excluding these 
> binary files which are rebuilt during the build process from the 
> debian source package results in a source package of smaller size.

The files are not binary, really, and not that big either.  That's why I 
consider it more relevant to keep source pristine.

Just yesterday I argued oppositely about a multimedia package that 
included Boost in its upstream tarball.  So I do agree with you, when 
size does matter, but not here :-)


> Is this the policy you are referring to
> http://www.debian.org/doc/debian-policy/ch-source.html#s-readmesource
> 
> I don't believe that applies in this case.

This (last sentence of that paragraph) is what I am referring to: 
http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#source-field

I tried just now and am actually surprised that I could not locate a 
corresponding requirement in Debian Policy itself: A driving principle 
when we recently developed Copyright Format 1.0 was to not introduce new 
requirements to content of the file, only to syntactic structure of it.  
I seem to recall this particular detail being discussed on debian-devel 
mailinglist about a year ago, but am too lazy to try find it now.


> Do you have reference to best practice or policy for this?

I can recommend that copyright format 1.0 document as a whole - it is a 
fairly short and nice read IMO.  No, I am not so good at reading fine 
manuals myself so have no good pointers to best practices.  They do 
exist, I am sure :-)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-osm-maint/attachments/20120626/98d0d31d/attachment.pgp>


More information about the Pkg-osm-maint mailing list