Hash: SHA1

darn, i wrote a long reply to this but then we had a power failure and
the mail is gone....

> On Tue, Dec 14, 2010 at 05:54:36PM +0100, IOhannes m zmoelnig wrote:
>> shouldn't all this exclusion be documented somewhere, e.g. in
>> debian/README.source?

On 2010-12-14 21:26, Jonas Smedegaard wrote:
> Instead of above, I include the upstream-tarball.mk CDBS snippet,
> declare with DEB_UPSTREAM_REPACKAGE_EXCLUDES what to exclude, and the
> "debian/rules get-orig-source" then automagically repackages a DFSG-free
> tarball from the pristine tarball offered upstream.
> And yes, in addition to that, I also mention the stripped parts in
> debian/copyright.  I personally consider such note required, but recent
> discussions about DEP5 indicated that not all agree with that.

On 2010-12-14 18:15, Reinhard Tartler wrote:
> I tend to script this process in form of a 'debian/get-orig-source.sh'
> script, which fetches the upstream source from svn, website or whatever,
> then calls another script 'debian/strip.sh' that removes the offending
> files.

i think this is exactly the reason why i wrote my q in the first place:
there seem to be a number of different approaches, and all work probably
equally well, if you are the maintainer of a package and the way fits
your workflow.
the problem i see is, that pkg-multimedia does collaborative
maintainance. some packages use this way and others that way, and there
is no real way for me as co-maintainer to find out which way was used
for the specific package. i don't think, looking at the git logs to find
out who imported the last file is a good idea.

neither is, checking whether CDBS was used in debian/rules or whether
there is a debian/get-orig-source.sh

wouldn't it be nice to have a short notice about how the sources got
imported (if that was done in any non-standard way)?
and again: wouldn't README.source be the right place?

Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

pkg-multimedia-maintainers mailing list

Reply via email to