PEAR installer in the wild
| From: | till | Date: | Thu, 06 Nov 2008 16:39:56 +0000 |
| Subject: | PEAR installer in the wild | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-51017@lists.php.net to get a copy of this message | ||
A while ago I started rolling all our small "cli tools" at work into
PEAR packages and while they are by no means perfect, almost every
time, I'm amazed how great and simple it is to install/uninstall
software and manage its dependencies through the little "pear"
command.
Especially when in comparison I have to deal with legacy code which
does not use any of the above. ;-)
So I think we ought to have a list of projects/people who use the
most-awesome PEAR installer to distribute their app/plugins/whatever.
So for example, check out:
http://solarphp.com/
http://www.magentocommerce.com/wiki/packaging_a_magento_extension
http://geeklog.org/
http://ezcomponents.org/
http://phpDoctrine.org/
http://phpundercontrol.org/
http://www.symfony-project.org/
http://code.google.com/p/xinc/
http://pecl.php.net/
http://midcom-project.org/
(Incomplete, and in no particular order.)
I'm sure there are more projects (there is also a channel list
somewhere on our website) and even companies who use the PEAR
installer to deploy applications. So wouldn't it make sense to
showcase that?
I know I just said there is a list, but what I really want is to
create a buzz and get some opinion on there why people use the PEAR
installer, vs. the infamous "unzip and go". It should also go into a
more promiment spot (frontpage, rotate show cases?).
A lot of people always perceive installing through "pear install foo"
as a overhead, because (I think) they don't know better. And
real-life-examples tend to work much better on those people than a 100
pages in the manual exercising why this is great. We all know (Don't
we?) that the little overhead it may add ("You need a working
install") is easily outscored by all the benefits of a managable
software installation and dependency tracking.
On a sidenote - we [PEAR] would also get some exposure from it since
some of these projects get way more attention and press than we do.
:-)
This [sh,c]ould go into the redesign thread from a week or two ago.
Thoughts?
Till