[pkg-php-pear] [Pkg-php-pear] On PEAR packaging

[Gunnar Wrobel]

Hi Mathieu,

Quoting Mathieu Parent <math.parent at gmail.com>:

> Hello,
>
> I have uploaded version 0.1 of the package to unstable (it should pass
> NEW first, but this seems fast those days: thanks to the ftp team).

Great!

>
> Still TODO, on the pkg-php-tools package:
> - (maybe) change the algorithm to name packages?

If possible yes. The short name of a PEAR channel can be identified by  
looking at the channel.xml - see "suggestedalias" in  
http://pear.horde.org/channel.xml

Another Horde developer mentioned that the "php-" prefix seems  
unnecessary on the applications (like "horde" and "kronolith"). I  
agree that prefixing those with "php-" does not make too much sense.  
It's a web application and it is not really really relevant if it is  
coded in PHP or Ruby. The applications were just named "horde3" and  
"kronolith2" before. Prefixing with "php-" seems useful for the more  
library like elements like "Horde_Date" ("php-horde-date"). But PEAR  
packages do not allow to distinguish between "library" and  
"application" type so this is knowledge we cannot evaluate  
automatically. If "php-" would be dropped for the applications it  
would need to be dropped on the libraries as well to stick with an  
automated approach. I'm tempted to do the package naming and the  
dependency resolution manually for the applications. Or would the  
debian naming conventions be okay with naming libs like "Horde_Date"  
just "horde-date"?

> - Find a way to avoid requiring pear-horde-channel and like

It is probably not needed anymore but I will have to check how that  
works with the Horde_Role package. That one is adding a channel  
specific configuration variable. But it might not actually need the  
channel definition and could live with a global configuration variable.

>
> Other TODOs:
> - package and upload horde4

That is probably something only you can do. It seems extremely  
cumbersome to check in all the packages to git. Is this something  
others can help with? How does the repository get upgraded once there  
is a new release?

> - Move almost all php-* packages to the new method

Since you sent patches to my horde-components tool: Do you plan on  
using that one for the Horde packages? Would you like it to be useable  
for other PEAR packages as well? So far recognition of remote packages  
is limited to the ones from pear.horde.org but it would be easy to  
extend this to other channels as well.

Cheers,

Gunnar

>
> Am I missing some TODOs?
>
> Regards
> --
> Mathieu

-- 
Core Developer
The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de