On 6/13/12 11:46 PM, cdamian wrote:
Yes, I am a bit worried that PEAR will get obsolete too. But I think it
is different for the components. They are used by PEAR packages and you
need the dependencies there.
When installing tools like phpunit and phpqa related stuff I am glad
that I can install them with PEAR or distribution installer and have the
dependencies automatically installed and updated. They will be used by
different projects I am working on.
It is different for projects that use frameworks, there the composer
makes sense because you want to have control over all your dependencies
in the git repository. I usually don't include phpqa or tools in
composer files.
On the other hand: I know have to deal with a lot of ruby projects
(puppet, vagrant, cucumber, ...) they tend to bundle all libraries and
sometimes even ruby itself, because of the dependency hell they are in.
Once a security problem is found in a central library I will have to
update all ruby projects.
I don't know how much work it is to keep the PEAR stuff up for the
components, but it certainly makes my life easier at work and as Fedora
packager.
PEAR packages are not going to be removed anytime soon. My point was
that if you are going to contribute to Symfony, using PEAR is probably
not the best option.
Fabien
On Wednesday, 13 June 2012 18:59:47 UTC+2, Fabien Potencier wrote:
Frankly, the PEAR packages are more or less obsolete as we now have
Composer. Installing Symfony or any other framework for that matter
globally on a system does not make much sense.
Fabien
--
Fabien Potencier
Sensio CEO - Symfony lead developer
sensiolabs.com <http://sensiolabs.com> | symfony.com
<http://symfony.com> | fabien.potencier.org
<http://fabien.potencier.org>
Tél: +33 1 40 99 80 80
On 6/13/12 6:47 PM, Shawn Iwinski wrote:
> What do you all think about adding the component tests that are
> available in the source repos to the PEAR packages? I know
personally
> there were a couple issues I had and having the unit tests to run
would
> have have most likely found the problem earlier than I did
manually. I
> wanted to get some opinions before actually filing a request.
>
> Shawn Iwinski
>
> --
> If you want to report a vulnerability issue on symfony, please
send it
> to security at symfony-project.com <http://symfony-project.com>
>
> You received this message because you are subscribed to the Google
> Groups "symfony developers" group.
> To post to this group, send email to
[email protected] <mailto:[email protected]>
> To unsubscribe from this group, send email to
> [email protected]
<mailto:symfony-devs%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=en
<http://groups.google.com/group/symfony-devs?hl=en>
--
If you want to report a vulnerability issue on symfony, please send it
to security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
