Including the orig tarball in svn

Fabian Fagerholm fabbe at paniq.net
Tue Jun 13 08:34:57 UTC 2006


On Tue, 2006-06-13 at 15:46 +0800, Paul Wise wrote:
> I just found out from importing stuff into pkg-flash that it isn't.
> Surely all the people using svn.d.o don't work like that? There must be
> something we are missing.

Yeah, I think so too. I randomly sampled the repos on svn.d.o that have
names starting with pkg-, and I found that people use a multitude of
different svn layouts. Some have top-level trunk, branches and tags
dirs, some store several source packages with their own trunk, branches
and tags dirs, some have trunk/debian, some store the debian dir
directly in trunk, some appear to use mergewithupstream and some aren't,
storing the upstream code as well.

The situation isn't much better than when I first started using
svn-buildpackage. There is no clear "best option" to choose, and for a
given combination of tools, there may in fact be no good option at all,
because the requirements of each tool prevents the useful features in
other tools, or the most useful feature of one tool make the other tools
cumbersome to use...

I don't have much extra time now, but if you want, we could start
adressing this issue by choosing a set of tools and rework them to fit
debian packaging better. svn + svn-buildpackage + [some patch system] +
pbuilder + piuparts + lintian + linda would be a good set. (Another one
would use bzr but I've never used it for anything real.)

-- 
Fabian Fagerholm <fabbe at paniq.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-synfig-devel/attachments/20060613/8c02dbad/attachment.pgp


More information about the pkg-synfig-devel mailing list