[php-maint] An automatic script to build PEAR packages
atomo64+debian at gmail.com
Tue Dec 29 23:50:28 UTC 2009
2009/12/26 Thomas Goirand <thomas at goirand.fr>:
> Thanks for your answer,
> Raphael Geissert wrote:
>> Yes, but we need to come up with a better workflow than the current
>> "just send a RFS to -mentors CC'ing pkg-php-devel".
> I do agree with that. I'm currently working together with "Roberto C.
> Sanchez" <roberto at connexer.com> that checks and uploads all the packages
> that I send to him. So far, it has been working quite ok, but as the
> number of packages are growing, I can see that using a single sponsor
> might not be the idea way, which is why I'm asking you guys.
I don't know who else of the others here have been sponsoring packages lately.
I surely can help sponsor some.
> Let's say if the workflow is that I create or update php package, then I
> send a mail with the link of my .dsc file on this list, then one of the
> member of the pkg-php team review it and upload, instead of just asking
> -mentors, would you think it's the way to go?
The procedure I'd prefer would be:
* You prepare the package, if you don't have a sponsor you send a RFS
to here and -mentors
And then if I say I'll sponsor it, I review it and give you feedback
for you to improve the package over and over again until it is ready.
Finally, I upload it and when there are updates (bug fixes, new
version, etc) you contact me.
I really need to put up some sponsoring guidelines, as I have a set of
> Now, few years ago, I applied on Alioth to be a member of the php team,
> but I guess because I didn't introduce myself properly, I got rejected
> after MONTHS. Now I understand better that communication in Debian is
> very important. Would you guys accept me this time? I do believe that I
> made quite some progress with my packaging skills too ... :)
As long as your intentions are explained there's no reason to reject anyone.
Please request to be added via the alioth project page.
>> Send me an email with links to the .dsc of the PEAR packages and I'll
>> check them.
> Sure! Here's the ones to check for update:
Ok, will check them. When do you plan to update php-net-ping?
> And here's some NEW packages (no ITP yet, if you tell me they are in
> good shape, I'll ask for an ITP and let you know (yes I know, I should
> the the opposite way... :) )):
Let me know when you've updated them to include the ITP bug closer.
> The goal of the one just above is to have php-text-captcha (and all its
> dependencies) working as I need a good captcha system. I didn't try it
> yet, so I'm not sure yet if this captcha is efficient. Has any of you
> tried, and know if it's worth the effort to have it packaged in Debian?
> I may give up if someone says I should, or if there is a better alternative.
It's been a while since I've last used it. Nowadays I would use
> Also, I asked Roberto to sponsor these:
> because I intend to have eXtplorer (a web file manager) in SID as well,
> and these are dependencies. You might want to check with Roberto first
> before doing any sponsoring work on them, to avoid double work here.
I won't touch those as you already asked him.
> Another question: what to do when I see on the pear website that a
> package seems unmaintained, but we need it by the way to satisfy some
> dependencies? Have you guys talked about it in a previous thread?
Just like we do here at Debian: one offers to maintain the package (or
work on it via the QA group.)
>> Oh and do you like git or svn or any of the other vcs' supported by
>> alioth? some time ago the plan was to get all the pear stuff under the
>> pkg-php umbrella.
> I've used CVS a lot, and at the end I hated it (no Unix right
> management, commits based on files, etc.). Then SVN is more or less the
> same, as much as I could see. But I don't really know it. I switched
> directly from CVS to Git, and I love it.
> So, if you guys are using SVN, I will never be able to follow (I do not
> want to learn a system that I consider old and retrograde), but if you
> guys are using Git, I'll be more than happy to use it. How are you going
> to work it out? Will it be one big Git repository for all the php-*
> packages (which would make sense), or would it be a single repository
> for each pear package (not sure it would make sense considering the size
> of each package)? Should I then send patches using git-format-patch,
> setup my own public repository, or even use the one on Alioth? Remember
> I'm still not a DD (a volunteers to be my AM would be more than welcome).
We have svn and git repositories setup and in use.
Check the way the current packages are organised in the repositories.
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net
More information about the pkg-php-maint