r2528 - in packages/trunk/vdrift/debian: . patches + new DGT policy check proposal

[Gonéri Le Bouder]

On Thu, Apr 05, 2007 at 12:47:06PM +0300, Eddy Petrișor wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Gonéri Le Bouder wrote:
> 
> (Please reply to the list, you know I read it :o)
> 
> > On Thu, Apr 05, 2007 at 01:03:29AM +0300, Eddy Petrișor wrote:
> >> Gonéri Le Bouder wrote:
> >>> +	msgfmt -c -o vdrift-2007-03-23-src/po/nl.mo vdrift-2007-03-23-src/po/nl.po
> >>> +		vdrift-2007-03-23-src/po/nl.mo
> >> Can't these be integrated into the upstream build system?
> > It is but the data files are needed to complete the installation and I
> > don't want to hack the scons files just for this. The src and data
> 
> OK, but this gives me an idea ...
> 
> > should be copied in the same directory to complete correctly upstream
> > install process.
> 
> And the idea is to add a supplemental games policy check for our
> packages in the autobuilder[1][2], so that we make sure we don't
> diverge too much from the upstream code and we make sure we give
> them back patches we have.
> 
> 
> The check might roughly do something like:
> - - count the files in debian/patches, if any, and warn if their
> number is too big
> - - compute the size of the debian/patches directory and warn if their
> cumulated size is too big
> - - warn when the diff from one package is too big (with means to
> define what is normal, probably through a autobuilder configuration
> or some svn property associated to the package)
> - - or warn when the debian diff.gz makes a leap in size from one
> release to another (this would have to be persistent somehow, and
> should be overriddable through svn somehow, so maintainers can have
> a way to say "I have checked the leap and is ok")
IMO, this depend to much on the package context and it'll be hard to
create a good check script for that.

> P.S.: BTW, isn't it high time to make a tools area in our repo and
> move the autobuilder[2] there? Gonéri?
Absolutly.

Cheers,

      Gonéri