merge edit

don't merge - if/when other packages are documented within wikipedia this page could become enormously long. --jazzle 06:03, 2 October 2006 (UTC)Reply

I agree with jazzle. Do not merge individual packages into this page! --thesaur 18:34, 30 October 2006 (UTC)Reply

I agree also. This page is for what PEAR is, not what its components are. Emanla Eraton 22:43, 5 November 2006 (UTC)Reply

Aporte edit

y cual es el aporte que hacen uds desvirtuando un tema en ves de hablar de el??

por mi parte no me queda algo claro, en los parametros que se le deben pasar al array dentro de smtp en pear, existe uno que se le debe agregar al wiki, al que estoy viendo en forma particular:

$wgSMTP = array(
 'host'     => "localhost",
 'IDHost'   => "domain for MessageID",
 'port'     => 25,
 'auth'     => false,
 'username' => "my_user_name",
 'password' => "my_password"
);

el que esta marcado en negrita, se supone que es un parametro para smtp definido en pear, pero en la pagina del proyecto pear [1], en a seccion parameter, no aparece ese parametro por ningun lado en smtp, asi, alguno de uds podria, por favor, decirme en que consiste ese parametro? y que efecto tiene en el smtp?, ademas. el codigo anterior, va dentro del localsettings? o dentro de mail.php??

muchas gracias Elpct82

English only here. --Hm2k (talk) 17:05, 12 March 2009 (UTC)Reply

PECL vs PEAR ? edit

If PECL has spun off from PEAR why does the PECL page redirect back here, rather than having its own page? What is the difference between the two? Can someone at least add a section explaining how they differ? 13:55, 8 March 2008 (UTC)

Requested move edit

The following is a closed discussion of the proposal. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the proposal was Move Parsecboy (talk) 00:08, 18 March 2009 (UTC)Reply

PHP Extension and Application RepositoryPEAR — It is better recognised as PEAR, not the full name. — Hm2k (talk) 17:05, 12 March 2009 (UTC)Reply

Survey edit

Feel free to state your position on the renaming proposal by beginning a new line in this section with *'''Support''' or *'''Oppose''', then sign your comment with ~~~~. Since polling is not a substitute for discussion, please explain your reasons, taking into account Wikipedia's naming conventions.
  • Support A search of periodicals using Google News shows many more uses of PEAR[2] than the full name. dissolvetalk 22:27, 13 March 2009 (UTC)Reply
  • Support The [PEAR website] greatly prefers PEAR to the full name. The naming conventions state Acronyms should be used in page naming if the subject is... widely known and used in that form, and a search of Google Groups clearly shows that [PEAR] is almost exclusively preferred to ["PHP Extension and Application Repository"] (115,000 vs 294 results). Google Groups is also searching forums for web developers, who are the main users of PEAR. --The Son of Man (talk) 00:53, 16 March 2009 (UTC)Reply

Discussion edit

Any additional comments:
The above discussion is preserved as an archive of the proposal. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

compared to CPAN edit

Unlike the Comprehensive Perl Archive Network (CPAN) archives, which PEAR took as its model, PEAR packages do not have implicit dependencies so that a package's placement in the PEAR package tree does not relate to code dependencies. Rather, PEAR packages must explicitly declare all dependencies on other PEAR packages.

unless I miss something subtle in this description, I believe it is wrong. Perl modules (CPAN or not) do not have any implicit dependencies, the package hierarchy is purely for human consumption, which is to say Foo-Bar distribution does not depend on Foo distribution, unless is is specified as such in the Makefile.PL, hence this is also an explicitly declared dependency system. --68.48.38.184 (talk) 03:17, 9 February 2012 (UTC)Reply

PEAR2 Pyrus - not dead as implied? edit

> The last release is from March 2011 and its development might have been discontinued due to the popularity of Composer.

I guess the article is quite unclear in regards to (Pear vs. Pear2 vs. Pyrus) since the current last release of Pear2 seems to be from April 2020 with various releases over the years [1]. Compared to that, the last commit to the Pyrus project on github is from July 2014 [2].

Unfortunately, I lack the background knowledge to update the article and clarify the current situation as is. Rehierl (talk) 12:45, 3 November 2020 (UTC)Reply

References