On Sun, Apr 04, 2010 at 09:16:26PM +0200, Reinhard Tartler wrote:
On Thu, Apr 01, 2010 at 23:00:18 (CEST), Adrian Knoth wrote:

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... ;)

TBH, this sounds not that unreasonable. However, you should be aware this means essentially, that we are forking upstream. Moreover, this also implies a totally different workflow compared to our other pkg-multimedia packages.

For consistency reasons, I'd prefer to not go that way with a team package. But I don't really work much on jack myself, so don't put too much weight in this opinion.

In my experience the workflow need not be very alien to normal git-buildpackage:

  * Reserve branches master*, upstream* and pristine-tar for Debian
  * Merge upstream release tag into "upstream" before tarball import

That's it!  Really!

 - 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