On Thu, Apr 01, 2010 at 11:00:18PM +0200, 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... ;)
I do want to setup a tighter integration between Debian packaging VCS and upstream VCS. Just very important to me to emphasize that is is in _addition_ to the use of tarballs, not _instead_ of it.
It seems to me that upstream use SVN, not Git. Is that correct?Would upstream perhaps be interested in maintaining a "bridge" - i.e. a Git instance mirroring the SVN, either pushed by an SVN hook or through cron?
I believe that will provide the most reliable way of keeping those VCSes in sync.
I am willing to help guide in the setup of an SVN→Git bridge.(might be that a deroute through Bazaar or other more convoluted setups are more potent, I just don't know how so cannot help there at all)
- Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
_______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
