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

[Thomas Goirand]

sean finney wrote:
> hi thomas,
> 
> some quick comments:
> 
> On Tue, Jan 26, 2010 at 06:31:15PM +0800, Thomas Goirand wrote:
>> If you want to build, just do this (example for php-crypt-cbc):
>>
>> git clone http://git.debian.org/git-http/pkg-php/php-crypt-cbc.git
> 
> Initialized empty Git repository in /home/sean/debian/php-crypt-cbc/.git/
> fatal: '/pkg-php/php-crypt-cbc.git' does not appear to be a git repository
> fatal: The remote end hung up unexpectedly
> 
> i don't know if this is from a missing update-server-info hook or something
> else.  however, the ssh url works for me:
> 
> git clone ssh://git.debian.org/git/pkg-php/php-crypt-cbc.git

I'm quite sure that I did a chmod +x on hooks/post-update, and ran git
--bare update-server-info manually on each Git repo. I am unsure what's
going on here. Help anyone?

> 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)

I've been asking about 3 times what is your branching practice, as some
differs. I still don't have an answer to that question, and it also seem
that different team/DD have different habits. Please let me know!

Also, nothing prevents you from using git-buildpackage either if you
like it, I was just telling of what I use.

> 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.

I'll fix that, and get back to the list when fixed. Thanks for taking
the time to have a look and highlighting it.

Thomas