Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Tests in PEAR packages?

Received: by 10.180.109.195 with SMTP id hu3mr2119030wib.0.1339650370320;
        Wed, 13 Jun 2012 22:06:10 -0700 (PDT)
X-BeenThere: symfony-devs@googlegroups.com
Received: by 10.216.51.197 with SMTP id b47ls82906wec.9.gmail; Wed, 13 Jun
 2012 22:06:02 -0700 (PDT)
Received: by 10.180.83.74 with SMTP id o10mr61454wiy.1.1339650362656;
        Wed, 13 Jun 2012 22:06:02 -0700 (PDT)
Received: by 10.180.83.74 with SMTP id o10mr61453wiy.1.1339650362647;
        Wed, 13 Jun 2012 22:06:02 -0700 (PDT)
Return-Path: <fabien.potenc...@symfony-project.com>
Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174])
        by gmr-mx.google.com with ESMTPS id x8si1912497wif.3.2012.06.13.22.06.02
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 13 Jun 2012 22:06:02 -0700 (PDT)
Received-SPF: neutral (google.com: 74.125.82.174 is neither permitted nor denied by best guess record for domain of fabien.potenc...@symfony-project.com) client-ip=74.125.82.174;
Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 74.125.82.174 is neither permitted nor denied by best guess record for domain of fabien.potenc...@symfony-project.com) smtp.mail=fabien.potenc...@symfony-project.com
Received: by weyu7 with SMTP id u7so1217521wey.33
        for <symfony-devs@googlegroups.com>; Wed, 13 Jun 2012 22:06:02 -0700 (PDT)
        d=google.com; s=20120113;
        h=message-id:date:from:organization:user-agent:mime-version:to
         :subject:references:in-reply-to:content-type
         :content-transfer-encoding:x-gm-message-state;
        bh=qGzzV4MFpn0OxSj/zhPE62/YDul/uWgKbqxj1RzGbFY=;
        b=edDM12u5uk0HmLHiH9ZGitAVqP24rGT9+zxrFXWYmyg/duLrwzWnLbptmQYLrUGi3L
         XzrVIB8/H51bO3uW+NAtKDJb1Y8EC5EWsGGhaO8m5eTjEsR5C8Yr12EotS25B4Bij6Qh
         HyCCI4hEN4DDKV54YTEBXFkTd7BHJ56//4wtCMpZyMMUPJhQyw/8/EeYhLUdPMTxKz3s
         zqu1jKr5i9PiQL2nfvCHcLCEB1/RgtrsTuJNKg83od+5Dvi6swzLcnmpH25zqv4miIdt
         +AWkNWQ2pC8S9nZvjdebE242XKIKkYWfeNG1gfxciRaWBv9JsazDxdGWGY71VpTVkMii
         U6WQ==
Received: by 10.216.213.143 with SMTP id a15mr186215wep.156.1339650362007;
        Wed, 13 Jun 2012 22:06:02 -0700 (PDT)
Return-Path: <fabien.potenc...@symfony-project.com>
Received: from Fabiens-MacBook-Air.local (vln78-1-82-238-161-203.fbx.proxad.net. [82.238.161.203])
        by mx.google.com with ESMTPS id hv7sm16667416wib.0.2012.06.13.22.05.59
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 13 Jun 2012 22:06:01 -0700 (PDT)
Message-ID: <4FD97137.4010...@symfony.com>
Date: Thu, 14 Jun 2012 07:05:59 +0200
From: Fabien Potencier <fabien.potenc...@symfony-project.com>
Organization: symfony
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: symfony-devs@googlegroups.com
Subject: Re: [symfony-devs] Tests in PEAR packages?
References: <997240d2-0079-4d0e-8ccc-8a46280b3bdf@googlegroups.com> <4FD8C703.2070...@symfony.com> <c88b614f-1841-4edb-b8f3-bb1b23fa59c4@googlegroups.com>
In-Reply-To: <c88b614f-1841-4edb-b8f3-bb1b23fa59c4@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkFIeL2WO4T88nXERdybEkm17e2HS6UhJN6mtBL4Rme4atxXwYzKIVAS11pwt6QGJa9lUju

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 th=
e
> 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=20
that if you are going to contribute to Symfony, using PEAR is probably=20
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=C3=A9l: +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 ru=
n
>     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 Goog=
le
>      > Groups "symfony developers" group.
>      > To post to this group, send email to
>     symfony-devs@googlegroups.com <mailto:symfony-devs@googlegroups.com=
>
>      > To unsubscribe from this group, send email to
>      > symfony-devs+unsubscribe@googlegroups.com
>     <mailto:symfony-devs%2Bunsubscribe@googlegroups.com>
>      > For more options, visit this group at
>      > http://groups.google.com/group/symfony-devs?hl=3Den
>     <http://groups.google.com/group/symfony-devs?hl=3Den>
>
> --
> 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 symfony-devs@googlegroups.com
> To unsubscribe from this group, send email to
> symfony-devs+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=3Den