Including the orig tarball in svn

[Fabian Fagerholm]

On Tue, 2006-06-06 at 22:54 +0800, Paul Wise wrote:
> At the moment, we have all the upstream source code in SVN, I mean we
> should use the mergewithupstream (or whatever it is) so that only the
> modified files are committed.

I find mergewithupstream a little bit annoying, because it means that
you have only the changed files in the source tree. For a package with
no changes to upstream, only the debian directory will be visible in
trunk. So if you want to make a change to an upstream file, you first
have to extract it from the upstream tarball, make your changes and
finally add the file to svn.

Having the complete upstream source in trunk means it's easy to check
whatever file you need. Also, the files are only committed once, so the
space waste is not that bad.

Also, mergewithupstream interferes with patch systems that we may want
to use later. For example, dpatch becomes hard to use if
mergewithupstream is on.

Or has svn-buildpackage become smarter since I last checked? :)

> > What I would do would be this (from the root of the entire repository):
> 
> Sounds good.

I'm finally adding the tarballs dirs to svn now.

-- 
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/20060612/2e8bb522/attachment.pgp