On Tue, May 08, 2007 at 10:43:46AM +0200, Michael Hanke wrote:
> Even when I split the package into data and binaries. As soon as a
> single file gets updated I have to bump the version and everyone has to
> download the whole package again.
I was speaking about splitting the _source_ package, so this is not a
problem. Actually you may want to persuade upstream to de-couple the
data from the code; why _they_ want to generate a single huge
distribution file if most part of it does not change from release to
release?
> But you are of course right, that having it all properly packaged in the
> archive is by far the best way to do it (from the user perspective). I'm
> just not sure whether it is useful to put this very, very special
> interested data in there?
It might turn out that packaging the data in this case is really not
worth it. However how about creating a common package with the wrapper
code? Or at least a debhelper script? That way the wrapper code can be
kept at a single place, and all packages with similar problems can be
converted to use it.
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
