[Pkg-mythtv-maintainers] Re: IVTV Debian packages

[Mark Purcell]

On Monday 27 March 2006 23:02, you wrote:
> > I have also injected 0.6.0 into the svn archive, although we might
> > like to switch to dpatch or cdbs.
>
> The patches are usually pretty minor so that might be overkill, but lets
> play it by ear.

No problems..

The advantages of dpatch/ cdbs is it keeps the patches visable and clearly 
separated from the .diif.gz.  Then again the learning curve is steep.  
Initially I was a little sceptical of the mertits, but for group maintenance 
it does work well.

> > How have you got your svn-buildpackage setup currently?
>
> I just kind of muddled through so I don't know if I'm using a good way
> or not...
>
> I have /trunk/ivtv as the working package source and /vendor/ivtv/0.6.0
> and /vendor/ivtv/current with the pristine upstream stuff. I was
> expecting the update procedure to be something like:
>       * checkin new upstream to /vendor/ivtv/0.6.1
>       * copy it to /vendor/ivtv/current
>       * merge into /trunk/ivtv
> I was aiming for option A.B. as described in
> in /usr/share/doc/svn-buildpackage/PRINCIPLES.gz.

Hmm,  With the other project I have been working with (kde-extras & pkg-voip) 
on alioth we have tended not to have the upstream actually stored in the 
archive, rather there is an empty tarballs/ directory where it looks and 
merges at build time.

Even with readonly access you should be able to grab a read copy of the 
archive to build.
Drop a copy of the orig.tag.gz file into the tarballs directory and then 
svn-buildpackage should work.

Then again pkg-mythtv is a new svn archive  so we can pretty much set it up as 
we like.

> I got 0.6.1 working for the version of the package on my website, I'll
> port that into the alioth repo once I have access and some spare
> minutes. The new release was purely a build issue fix and made all the
> videodev2.h hackery I did in 0.6.0 obsolete so it really cleans things
> up. But as I worked round the problem in 0.6.0 there is no urgent need
> to upload IMHO.

0.6.1 build fine with your package, so I have also uploaded to NEW and updated 
svn.  But feel free to tidy up in svn and then  I can release directly from 
there..

Mark