Hi, On Tue, Sep 08, 2009 at 10:21:38AM +0800, Jason Heeris wrote: > 2009/9/8 Ryan Niebur <[email protected]>: > > > okay, I think I understand now. how about just using "debuild" then? > > why use svn-buildpackage if you don't want it to merge with upstream? > > Because I'm operating out of my upstream WC. To put it another way > I've already "merged with upstream," (just not the tarball) but I'm > still using an SVN checkout, so (p)debuild chokes. > > I could export my WC and packaging, but it's an extra few steps and
you don't need to export at all. just run "debuild" in the working copy. if you're getting lintian warnings about .svn, it means that you need to fix your configs, see the man page of debuild. this should be a fine workflow for test builds. > then I have to copy stuff back to my packaging WC to commit (which is > why I like svn-buildpackage in the first place, I can just work on > packaging out of a WC). The trouble is, svn-buildpackage in merge mode > only allows merging with a tarball, and this is about 1% of my usage > (which maybe indicates a lack of planning on my part :P). I had that > set so that it didn't try to store the entire upstream stuff > unnecessarily, and I can keep the packaging up to date as we work on > the software itself. > > (To be honest, I'm still figuring out the best workflow for packaging, > so maybe there's a better way that hasn't occurred to me.) > Cheers, Ryan -- _________________________ Ryan Niebur [email protected]
signature.asc
Description: Digital signature
