make monolog installable through pear about monolog

[till]

I'd propose to use pyrus. Creating the necessary files is trivial with it and it supports both pear1 and pear2 style.

I can send you a pull request later today.

[stof]

I don't see what a pull request should have to do with this. The pear channel does not need to be in the github repo as the PEAR file is useless for all people getting it using git. If you look at Symfony2 for instance, there is no PEAR files in the components.

[till]

You'll need a package.xml and a couple .php files for pear/pyrus to work. I'd contribute that basically and document how it works. Is that acceptable for you? ;-)

[stof]

@til What I say is that I'm really not sure that these file should be placed in the github repo as they are not needed for all people using git instead of PEAR to install Monolog. Symfony does not put these files in the github repos either.
@Seldaek what do you think about it ?

[Seldaek]

The package will be hosted at http://pearhub.org/projects/Monolog - once they crawl the repo.

[Tyrael]

nice, thanks.

[stof]

Note that according to the page, Monolog 1.0.0 is available through pearhub. @Seldaek you should maybe add a link in the readme.

Edit: the release failed for pearhub

[Seldaek]

Yeah I don't know why the build failed, it's not very descriptive. I tried changing the repo url to http scheme instead of git, doesn't seem to help. I'll message the guy.

[till]

[ Real men run their own pear channel. ;-)) ]

@jordi: I didn't know symfony didn't commit their XMLs. Do they just live outside the repo period, or what's the idea? Having them in the repository allows people to run code from trunk (or master) and manage it via PEAR as well.

@stof: The name is TILL. Two L.

[stof]

sorry for the name.

For your first point, I don't understand what you mean. Do you imply that someone willing to use the master branch for monolog would setup its own pear channel ?

[Tyrael]

you don't have to set up a channel to build and install a package.

[notlaforge]

@till yes? :P

[till]

@stof:

So assuming you guys would use pyrus to manage the required XML's etc..

Whenever you guys update and push, you do pyrus make this updates the include XMLs etc.. You commit those changes and push to github.

Then, when I pull on my side I can use pyrus or pear to install the code from github:

pyrus install package.xml

Or:

pear install package_compatible.xml

Does that make sense?

[till]

@jordi: ;-), I meant @Seldaek.

[Seldaek]

Pearhub is now fixed