[pkg-php-pear] [Pkg-php-pear] On PEAR packaging
wrobel at horde.org
Sun Jul 24 08:43:35 UTC 2011
Quoting Mathieu Parent <math.parent at gmail.com>:
> 2011/7/23 Gunnar Wrobel <wrobel at horde.org>:
>>> Updated TODO for "components":
>>> - use algorithm from pkg-php-tools (via a wrapper)
>> What should the wrapper do? I would assume I simply call the tool you coded
>> as the debian packaging helper in the components module relies on your
>> debian packaging helper anyway.
> Yes, you now need pkg-php-tools v0.3 (just uploaded, but also in git)
> and the attached patch.
Seems to work fine here though I only did a few test packages so far.
>>> - recursive template (for debian/source/format and debian/patches)
>> Ok, will do as soon as possible.
Implemented and pushed.
>>> - allow to apply several template folders (one generic and one specific)
>> Can you detail what you need here? How should the different folders be
> I need to have most of the files from the current template, and
> override some of them with package-specific files (changelog, patches,
> copyright, possibly more). An hook after the templating and before the
> build is also OK.
Implemented and pushed.
The debian components.php helper will now use the recursive template
directory handler for the indicated --templatedir TEMPLATEDIR (default
"data/debian/templates" in components). Besides that it will check for
the existence of "TEMPLATEDIR-PKG_NAME" and
"data/debian/templates-php-horde-exception-1.0.4"). If they are
present then their content will also be used as a recursive template
directory. "TEMPLATEDIR-PKG_NAME" will unconditionally overwrite stuff
from "TEMPLATEDIR" if there are templates with the same file name
present. "TEMPLATEDIR-PKG_NAME-PKG_VERSION" will then overwrite the
other two as it is the most specific identifier.
Both package specific variants can be symbolic links so it should also
be possible to join template directories for several packages.
Does that provide you with the possibilites you need for package
specific templates or is something missing?
>>> Updated TODO for Debian:
>>> - create ITPs for all packages
>> Sounds like this is something you will do.
>>> - write all the copyright files :-P
>> Sounds like this is something I will do :) ... We need to place a COPYRIGHT
>> or LICENSE file in each of the framework packages, right?
> I also need to check. But anything done upstream is better.
Will try to at least start on this tonight.
>>> - test, polish, test, polish
>> Once we are here we will broadcast this via horde.org and I also have
>> customers that will test those.
> I'm currently using the attached script to build almost all the packages.
>>> - upload to experimental first
>> Hope this is not too far away :)
> I will start this week, but as there are 94 packages on pear.horde.org!
> (I can build 123 packages from source. 20 others don't have
> package.xml, and 4 have a package.xml which doesn't validate)
Building from source is of course possible but is something that
should in no way end up as "real" Debian package. If the Horde project
didn't even package those up as PEAR packages yet, then Debian
packages shouldn't exist either. Any package not available on
pear.horde.org but present in git is a component that is purely in
development. There are no guarantees for those and it wouldn't be good
to torture users with them :)
>> Thanks for all your efforts with this. I'm glad to see it moving.
> I'm happy to have some free time. But it is flying ...
>> 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
The Horde Project
e: wrobel at horde.org
t: +49 700 6245 0000
pgp: 9703 43BE
More information about the pkg-php-pear