[Pkg-scicomp-devel] upstream source in svn

[Frank S. Thomas]

Hello,

On Tuesday 04 September 2007, Ondrej Certik wrote:
> Hi Steffen,
>
> > I commonly check out the full repositories from alioth svns, both for
> > commodity and curiosity. However, with SciComp I filled my local disk's
> > partition since all upstream source apparently comes with it. This was a
> > bit to my (and my disk's) surprise.
> >
> > Are you aware of the "merge" flag for svn-buildpackage? This way only the
> > Debian directory would be saved to the disk. The upstream bits would come
> > from the orig.tar.gz. Changes to upstream would have to be prepared via a
> > patch file. I find this to be very beneficial, particulary for frequently
> > updated upstream packages.
>
> we use it for some of the packages, for example libmesh, abinit,
> openmx etc. Actually, you don't even have to prepare everything as
> patches (although it is definitely cleaner), you can just put any
> files in the svn and svn-buildpackage will automatically create the
> diff.

Just BTW: If only changed files are added to the Subversion repository it is a 
good practice to commit the original version of the files first before the 
changed files are committed. This way allows that all changes to the original 
sources can be extracted as patches from the repository. Otherwise one would 
always need the .orig.tar.gz to see what was changed in the files in the 
repository.

Grüße,
Frank
-- 
Anmut bringen wir ins Leben;
 Leget Anmut in das Geben.
-------------- 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-scicomp-devel/attachments/20070904/3538be3c/attachment.pgp