On Tue, Aug 03, 2010 at 05:04:20PM -0400, Felipe Sateler wrote: > Hi all, > > I recently developed an interest in Code::Blocks, which is not currently > in Debian, and the current ITP has shown no real activity for over a year. > However, an upstream developer does provide unofficial debian packages, > and I would like to polish them and upload to Debian, acting as a > sponsor rather than co-maintainer. > > So, the problem is that currently the debian packaging lives in the same > subversion repository as upstream development, with the associated > problems (native package, or in a best case scenario a very dirty > diff;
I think this is a good option to avoid the dirty diff: >From http://wiki.debian.org/Projects/DebSrc3.0 ... * You don't have to repack the upstream tarball to strip the debian directory. (The debian directory is automatically replaced by the content of the .debian.tar.{gz,bz2,lzma} file at unpack time) ... > entanglement of upstream development with debian packaging development). > > If upstream were using git, the solution would be pretty simple, just > branch and merge from upstream as required (as done by many packagers in > debian). However, subversion is in use, and last time I tried a merge in > svn it was a complete disaster, so I'm not recommending that strategy. > What workflows could be used, to avoid a "fork"? -- Josué M. Abarca S. Vos mereces Software Libre. PGP key 4096R/70D8FB2A 2009-06-17 fingerprint = B3ED 4984 F65A 9AE0 6511 DAF4 756B EB4B 70D8 FB2A -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
