[php-maint] An automatic script to build PEAR packages

[Raphael Geissert]

2010/1/8 Thomas Goirand <thomas at goirand.fr>:
> Raphael Geissert wrote:
>> Please read about the Debian infrastructure and the services provided
>> by Alioth. I won't spend my time explaining you what a couple of wiki
>> pages perfectly document.
>> Don't take it personally, it's just that you need to be able to find
>> the solutions on your own. It's for your own good.
>
> Sure! I was not expecting anything else than a couple of links to the
> relevant documents that I couldn't find myself. I didn't need much, and
> now I do have the information that I was missing (even if it was kind of
> hard to find), like path to the git repo in alioth (thanks to the help
> of madduck on #debian-devel), and other stuffs.

Yes, just saw the backlog, but was http://wiki.debian.org/Alioth/Git
too hard to find?
Almost everything you need to know about alioth is right there.

> I have found this one
> the most helpful:
>
> http://www.eyrie.org/~eagle/notes/debian/git.html
>
> Before I put all of my packages in Alioth, can you clone this one, and
> let me know if it's as expected?
>
> ssh://alioth.debian.org/git/pkg-php/php-crypt-cbc.git

Er, no. Why do you think having the original tarball in a branch is
useful? if you want to use the tarball in tarball, which is strongly
discouraged, there's no need to ship the unpacked files either. N.b.
Nowadays, I don't think anyone would sponsor  a package with a tarball
inside a tarball.

And by taking a quick look at the package:
* Please add comments for lintian overrides on the overrides file
itself. It is easier to inspect them that way.
* Overriding that lintian tag is incorrect, read its description and
get upstream to change the license. Why do you think that "Crypt_CBC
is part of PHP"?
* debian/copyright: the Copyright years do not match those indicated
by the .php file.


>
> As per the above page, I have 3 branches: master, debian, upstream. Is
> this the way you think it should be / you like it?

For PHP we only use debian-<release> and upstream-<release> branches,
but if you can deal with three branches and you know what you are
doing it is fine.

Regards,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net