[Pkg-octave-devel] patch systems
On Sat, Aug 23, 2008 at 03:31:25PM +0200, Rafael Laboissiere wrote:
> * Thomas Weber <thomas-guest@alioth.debian.org> [2008-08-23 12:41]:
>
> > Author: thomas-guest
> > Date: 2008-08-23 12:41:41 +0000 (Sat, 23 Aug 2008)
> > New Revision: 2391
> >
> > Removed:
> > octave/trunk/debian/patches/50_include-cstring-mxarray.dpatch
> > Modified:
> > octave/trunk/debian/in/00list
> > Log:
> > Remove 50_include-cstring-mxarray.dpatch for both 3.0 and 3.1
> > The change was already in 3.1.51, but stupid dpatch didn't complain about the hunk
>
> Time to switch to quilt?
> http://blog.orebokech.com/2007/08/converting-debian-packages-from-dpatch.html
After the removal of 2.1; there's no sense in converting lots of
patches only to remove them shortly thereafter.
I watched the video of Martin Krafft's talk about packaging with
distributed systems and I seriously hope there's a simpler workflow:
with one branch for every patch, I would need a map to find my way around.
By the way, we have quite some documentation bugs against octave3.0,
that are fixed in the 3.1 branch. I don't intend to fix them now, but
have sent a mail to octave-maintainers, so Jaroslav can transplant them
into the 3-0-x branch.
Thomas
Reply to: