On Thu, Apr 01, 2010 at 11:00:18PM +0200, Adrian Knoth wrote:
On Thu, Apr 01, 2010 at 09:53:19PM +0200, Jonas Smedegaard wrote:

In short: I would very much like to volunteer to repackage the current vcs-tarball as pristine-tarball + vcs-patch. Is that acceptable?

Different approach: make us the jackd2 repository. ;) So we simply use git, wildly patch whatever we want, no need to wait for upstream to apply my patches and pull from their svn repo from time to time. ;)

This way, we can ship the extracted (and checked) waf code, strip *.dll from the package and all the other tweaks that will be required.

Might sound completely crazy, probably because it isi, but it surely has its advantages... ;)

It certainly has its advantages if upstream also use Git to then maintain upstream and our branches in a single Git. For packaging development.

But it still makes best sense to base our final releases on pristine tarballs (or not pristine, if upstream tarballs are not DFSG-free).

Is it ok with you that I repackage from the current vcs-tarball to pristine-(or-repackaged)-tarball + vcs-patch?

We can then _also_ extend to track upstream Git as well, but let's do one thing at a time. You can have a look at e.g. "debcheckout sugar" and read its debian/README.source for a suggestion on how to do it. Or ask if that file is not easy to comprehend, and I'd be happy to elaborate :-)

 - Jonas

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

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to