On Sat, Jun 29, 2013 at 11:09:13AM +0800, Thomas Goirand wrote: > On 06/29/2013 08:30 AM, andrea rota wrote: > > these three php-symfony-* packages i'm working on are dependencies for > > Composer, alongside two other PHP libraries which are only distributed > > via composer itself (not via any PEAR channels), whereas the Symfony > > components are distributed via both methods. > > > > i started packaging these Symfony components with the dh_phpcomposer > > helper as suggested previously on the pkg-php-pear list, but i see there > > are different opinions. > > My understanding of it isn't that there was 2 opinions, but that you > didn't know about pear.symfony.com. I didn't really follow the > dh_phpcomposer discussions, I'm sorry if that wasted some of your time. > > > i can re-package the Symfony components from pear.symfony.com if that is > > the preferred method, of course. > > Yeah, please do! here is a first attempt: http://anonscm.debian.org/gitweb/?p=pkg-php/php-symfony2-process.git [...] On Sun, Jun 30, 2013 at 01:24:37AM +0800, Thomas Goirand wrote: > On 06/28/2013 05:20 PM, Mathieu Parent wrote: > >> Another thing: I have noticed that what is used as upstream source is > >> > quite wrong for all packages. They should all be coming from > >> > http://pear.symfony.com/. In there, you will find packages the way they > >> > should: including a package.xml, so that we can use the PEAR things to > >> > get them installed, have a registry file, manage dependencies > >> > automatically, etc. Missing the package.xml is simply wrong, IMO. > > Again, those are not PEAR pkg. > > I think there's a miss-understanding here. I'm saying that we should use > what's in pear.symfony.com as it seems to be the same thing (and it > seems to be the same version), but in a PEAR package format. Am I wrong? > > (I'm taking about php-symfony-process, I haven't looked at other > packages yet) pear.symfony.com seems complete to me, providing latest versions of all the Symfony2 components also available via upstream git. i have used the existing naming scheme for this Debian package (php-symfony2-<component), however this will clash with substvars generated (for libraries from other sources only distributed via composer) by dh_phpcomposer: in composer/packagist, these same Symfony2 packages are labelled (by the Symfony project) as 'symfony/<component>' (e.g. symfony/process), which is correctly translated to php-symfony-process by dh_phpcomposer. I originally suggested using Provides: but Mathieu pointed out that Provides is not versioned (and i can see this being an issue with some fast-changing packages) - Mathieu suggested considering metapackages as well, which should indeed work here. However, when i tried adding a second binary package to debian/control for php-symfony2-process, building failed: ----- dh clean --buildsystem=phppear --with phppear dh_testdir -O--buildsystem=phppear dh_clean -O--buildsystem=phppear gbp:info: php-symfony2-process_2.3.1.orig.tar.gz does not exist, creating from 'upstream/v2.3.1' gbp:info: Exporting 'HEAD' to '/home/e402b82b49d23e6d2c7ff5f4ede872ab400fee6d/debian.org/packages/pkg-php/php-symfony2-process/build-area/php-symfony2-process-tmp' gbp:info: Moving '/home/e402b82b49d23e6d2c7ff5f4ede872ab400fee6d/debian.org/packages/pkg-php/php-symfony2-process/build-area/php-symfony2-process-tmp' to '/home/e402b82b49d23e6d2c7ff5f4ede872ab400fee6d/debian.org/packages/pkg-php/php-symfony2-process/build-area/php-symfony2-proces$ -2.3.1' dpkg-buildpackage -rfakeroot -D -us -uc -i -I dpkg-buildpackage: source package php-symfony2-process dpkg-buildpackage: source version 2.3.1-1 dpkg-buildpackage: source changed by andrea rota <a@xelera.eu> dpkg-source -i -I --before-build php-symfony2-process-2.3.1 dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean dh clean --buildsystem=phppear --with phppear dh_testdir -O--buildsystem=phppear dh_clean -O--buildsystem=phppear dpkg-source -i -I -b php-symfony2-process-2.3.1 dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building php-symfony2-process using existing ./php-symfony2-process_2.3.1.orig.tar.gz dpkg-source: warning: ignoring deletion of file Process-2.3.1/package.xml dpkg-source: info: building php-symfony2-process in php-symfony2-process_2.3.1-1.debian.tar.gz dpkg-source: info: building php-symfony2-process in php-symfony2-process_2.3.1-1.dsc debian/rules build dh build --buildsystem=phppear --with phppear dh_testdir -O--buildsystem=phppear debian/rules override_dh_auto_configure make[1]: Entering directory `/home/e402b82b49d23e6d2c7ff5f4ede872ab400fee6d/debian.org/packages/pkg-php/php-symfony2-process/build-area/php-symfony2-process-2.3.1' dh_auto_configure -O--buildsystem=phppear # Remove references of .gitignore sed -i 's@^.*\.gitignore.*$@@' */package.xml make[1]: Leaving directory `/home/e402b82b49d23e6d2c7ff5f4ede872ab400fee6d/debian.org/packages/pkg-php/php-symfony2-process/build-area/php-symfony2-process-2.3.1' dh_auto_test -O--buildsystem=phppear fakeroot debian/rules binary dh binary --buildsystem=phppear --with phppear dh_testroot -O--buildsystem=phppear dh_prep -O--buildsystem=phppear dh_auto_install -O--buildsystem=phppear dh_auto_install: only one binary package supported, got 2 make: *** [binary] Error 255 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 debuild: fatal error at line 1357: dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed gbp:error: Couldn't run 'debuild -i -I': debuild -i -I returned 29 ----- i guess i'd have to override dh_auto_install, but i'm not sure how best to go about it (i see for example that php-sabredav defines two binary packages in debian/control, but they use composer as build system: http://anonscm.debian.org/gitweb/?p=pkg-owncloud/php-sabredav.git;a=blob;f=debian/control;h=69a06c286f9d0d11b57268fc956b041e64c7d16e;hb=HEAD) other than this, feedback on this package is welcome. best andrea -- andrea rota Xelera - IT infrastructures http://xelera.eu/contact-us/
Attachment:
signature.asc
Description: Digital signature