>> Provides: php-composer(foo) = %{version}
I really like this idea and meant to bring it up before. Most upstream pkgs are going the composer route and even if we don't create our downstream pkgs using composer we should at least be able to find them by it. I know personally this would have saved me time with one pkg that already existed!
Also, I would like to make sure "foo" = "vendor/project".
Can we start using this now or should we wait?
On Sun, Mar 9, 2014 at 4:18 AM, Remi Collet <Fedora@xxxxxxxxxxxxxxxxx> wrote:
Le 09/03/2014 08:26, Guillaume Kulakowski a écrit :
> Hi,Must disagree.
>
> Good idea. Is there a page for that in the Wiki ?
>
> Some question:
>> So I(m going to start to move the dependencies from pear channel to
>> github sources.
> You d'ont use Comopser ? Because a rule missing:
> If comopser method exist, you SHOULD use it.
There is only, for now, 2 types of package.
- PEAR (the installer, using /usr/share/pear)
- Tarball (sources, using /usr/share/php)
Composer is absolutely irrelevant for system wide packaging.
Only benefit we have is the (quite good) description of dependencies in
the metadata file (composer.json). Nothing more.
So NO, I don't think we should prefer 1 method.
I think it sometine make sense to switch to "sources" (github or
something else) instead of pear, when pear channel is no more maintained
(sabredav) or very poorly maintained (symfony, phpseclib, ...). No other
reason.
Remi.
>
> No ?
>
>
> 2014-03-08 8:05 GMT+01:00 Remi Collet <Fedora@xxxxxxxxxxxxxxxxx>:
>> Hi,
>>
>> See :
>> https://github.com/sebastianbergmann/phpunit/wiki/Release-Announcement-for-PHPUnit-4.0.0
>>
>> This means that the PEAR channel is going to be deprecated.
>>
>> So I(m going to start to move the dependencies from pear channel to
>> github sources.
>>
>> Already done for php-phpunit-Version
>> https://github.com/remicollet/remirepo/commit/44d4e911d5abf05dbee29e65b70d58c746d7dfd4
>>
>> I have run some tests, phploc and phpcpd still work with this new
>> package layout.
>>
>>
>> Probably we need some Guildelines to facilitate such migration.
>>
>> My idea is:
>>
>> - pear package MUST (names from package.xml)
>> Provides: php-pear(foo) = %{version}
>> Requires: php-pear(bar) >= x.y
>>
>> - composer packages MUST (names from composer.json)
>> Provides: php-composer(foo) = %{version}
>> Provides: php-composer(foo) >= %x.z
>>
>> - composer packages SHOULD temporary provides
>> Provides: php-pear(foo) = %{version}
>>
>> - composer packages MUST not
>> Requires: php-pear(bar) >= x.y
>>
>> This allow us to track (using repoquery) pear dependencies, and this
>> temporary provides could be dropped when no more required.
>>
>> Of course this have to happen mostly in rawhide.
>>
>> Feedback ?
>>
>>
>> Remi.
>>
>> P.S. as PHPUnit 3.7 is a LTS version, I plan to keep it for some time in
>> Fedora <= 20 and EPEL <= 6.
>> _______________________________________________
>> php-devel mailing list
>> php-devel@xxxxxxxxxxxxxxxxxxxxxxx
>> https://admin.fedoraproject.org/mailman/listinfo/php-devel
>
>
>
_______________________________________________
php-devel mailing list
php-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/php-devel
_______________________________________________ php-devel mailing list php-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/php-devel
