http://blog.twig.sensiolabs.org/post/76626577337/pear-packages-wont-be-publi...
Are there any guidelines for packaging composer packages in the works?
Le 14/02/2014 16:18, Christof Damian a écrit :
http://blog.twig.sensiolabs.org/post/76626577337/pear-packages-wont-be-publi...
Are there any guidelines for packaging composer packages in the works?
There is no Guidelines as composer is just irrelevant for packaging.
- Composer target is bundled library in project vendor lib. - Pear target is system shared library.
You just have to package it as a simple library under /usr/share/php, as a lot are already packaged. When possible, PSR-0 compliant library, have to be installed for autoloader to work using default include_path.
The only benefit, for us, with composer is the (usually) well described dependencies in composer.json.
As an example, you can look at the php-symfony packages which have recently moved from PEAR channel to Github sources.
Remi.
php-devel mailing list php-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/php-devel
By the way, I will update php-twig-Twig to the latest 1.15.1 and I will submit a new non-PEAR pkg review request after the next release that does not use PEAR.
On Fri, Feb 14, 2014 at 10:35 AM, Remi Collet Fedora@famillecollet.comwrote:
Le 14/02/2014 16:18, Christof Damian a écrit :
http://blog.twig.sensiolabs.org/post/76626577337/pear-packages-wont-be-publi...
Are there any guidelines for packaging composer packages in the works?
There is no Guidelines as composer is just irrelevant for packaging.
- Composer target is bundled library in project vendor lib.
- Pear target is system shared library.
You just have to package it as a simple library under /usr/share/php, as a lot are already packaged. When possible, PSR-0 compliant library, have to be installed for autoloader to work using default include_path.
The only benefit, for us, with composer is the (usually) well described dependencies in composer.json.
As an example, you can look at the php-symfony packages which have recently moved from PEAR channel to Github sources.
Remi.
php-devel mailing list php-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/php-devel
php-devel mailing list php-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/php-devel
Le 14/02/2014 16:44, Shawn Iwinski a écrit :
By the way, I will update php-twig-Twig to the latest 1.15.1 and I will submit a new non-PEAR pkg review request after the next release that does not use PEAR.
As both extension (PHP and C) comes from the same sources, please include both in your package, so I can also orphan php-twig-ctwig.
/me plans a mass orphan.
I don't know why I would have to take care of upstream who don't care of downstream :(
Remi.
Will do
On Fri, Feb 14, 2014 at 10:49 AM, Remi Collet Fedora@famillecollet.comwrote:
Le 14/02/2014 16:44, Shawn Iwinski a écrit :
By the way, I will update php-twig-Twig to the latest 1.15.1 and I will submit a new non-PEAR pkg review request after the next release that does not use PEAR.
As both extension (PHP and C) comes from the same sources, please include both in your package, so I can also orphan php-twig-ctwig.
/me plans a mass orphan.
I don't know why I would have to take care of upstream who don't care of downstream :(
Remi.
php-devel mailing list php-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/php-devel
Remi -- Twig 1.16.0 has been released so I have started the new package. How do I create an "arch" sub-package in a "noarch" main package? I get "error: Arch dependent binaries in noarch package" when I try.
On Fri, Feb 14, 2014 at 10:50 AM, Shawn Iwinski shawn.iwinski@gmail.com wrote:
Will do
On Fri, Feb 14, 2014 at 10:49 AM, Remi Collet Fedora@famillecollet.com wrote:
Le 14/02/2014 16:44, Shawn Iwinski a écrit :
By the way, I will update php-twig-Twig to the latest 1.15.1 and I will submit a new non-PEAR pkg review request after the next release that
does
not use PEAR.
As both extension (PHP and C) comes from the same sources, please include both in your package, so I can also orphan php-twig-ctwig.
/me plans a mass orphan.
I don't know why I would have to take care of upstream who don't care of downstream :(
Remi.
php-devel mailing list php-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/php-devel
Le 07/07/2014 19:25, Shawn Iwinski a écrit :
Remi -- Twig 1.16.0 has been released so I have started the new package. How do I create an "arch" sub-package in a "noarch" main package? I get "error: Arch dependent binaries in noarch package" when I try.
You cannot, you have to do the opposite, an arched main package (the C extension) and a noarch subpackage (the PHP library).
Remi.
On Fri, Feb 14, 2014 at 10:50 AM, Shawn Iwinski shawn.iwinski@gmail.com wrote:
Will do
On Fri, Feb 14, 2014 at 10:49 AM, Remi Collet Fedora@famillecollet.com wrote:
Le 14/02/2014 16:44, Shawn Iwinski a écrit :
By the way, I will update php-twig-Twig to the latest 1.15.1 and I will submit a new non-PEAR pkg review request after the next release that
does
not use PEAR.
As both extension (PHP and C) comes from the same sources, please include both in your package, so I can also orphan php-twig-ctwig.
/me plans a mass orphan.
I don't know why I would have to take care of upstream who don't care of downstream :(
Remi.
php-devel mailing list php-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/php-devel
php-devel mailing list php-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/php-devel
php-devel@lists.fedoraproject.org
-
Christof Damian -
Remi Collet -
Shawn Iwinski