[php-maint] 13 php pear module ready in the Git to be sponsored

Ondřej Surý ondrej at debian.org
Tue Jan 26 15:04:50 UTC 2010


>> This will create the orig.tar.gz and build using a folder in /tmp, then
>> moving the results in .. (as I don't really like the Debian git build
>> tools, I hope you are fine with the way I do).
>
> there are two problems here.  first, yes at least I do have a strong
> preference for the existing build methods and tools (branch naming,
> practices, and tools).  doing things differently won't necessarily block
> your packages from being accepted into debian, but it will definitely
> serve as a deterrent for me (and i'd assume others) to help out.

Same here. Please use git-buildpackage.

> secondly, the packages do not build in a policy compliant manner, which
> is a more serious issue in terms of gaining acceptance into the archive.
> debian policy is pretty specific about which targets are mandatory in a
> source package's debian/rules file.  for example, debian/rules install
> does not create the installation tree, and debian/rules binary does not
> produce the deb.  as a general rule i wouldn't add to or modify the
> debian/rules interface (someone preparing an NMU should not have to
> know anything about a particular source package's "special" build
> methods), but the required targets are a hard requirement.

Use as much of debhelper 7 as possible (with few overrides) and use
quilt or even better 3.0 (quilt) dpkg format.

Ondrej
-- 
Ondřej Surý <ondrej at sury.org>
http://blog.rfc1925.org/



More information about the pkg-php-maint mailing list