[Pkg-scicomp-devel] upstream source in svn

Ondrej Certik ondrej at certik.cz
Tue Sep 4 05:45:16 UTC 2007


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.

> I apologize should this have been discussed before, not unlikely, admittedly.
> In that case I volunteer for a note on the project's home page on the svn
> policies. Should this be some new thought for this project, then I would be
> happy to give an example.

But I agree it should be used for all of the packages.

Ondrej



More information about the Pkg-scicomp-devel mailing list