mirror of
https://github.com/Seldaek/monolog.git
synced 2026-04-26 08:05:53 +03:00
[GH-ISSUE #37] make monolog installable through pear #8
Labels
No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/monolog#8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Tyrael on GitHub (Jul 10, 2011).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/37
as @fabpot planning to provide a pear package for Silex, it was brought up, that it would be good, if the dependencies could be also provided through pear:
https://github.com/fabpot/Silex/issues/82
I know that Monolog is/will be available through composer, but I think it would be a good idea, if the dependencies for Symfony2/Silex could be managed through one tool.
As Symfony2 and most of its dependencies available through pear, I think it would be logical to have a pear package for Monolog.
@till commented on GitHub (Jul 11, 2011):
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 commented on GitHub (Jul 11, 2011):
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 commented on GitHub (Jul 11, 2011):
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 commented on GitHub (Jul 11, 2011):
@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 commented on GitHub (Jul 11, 2011):
The package will be hosted at http://pearhub.org/projects/Monolog - once they crawl the repo.
@Tyrael commented on GitHub (Jul 11, 2011):
nice, thanks.
@stof commented on GitHub (Jul 11, 2011):
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 commented on GitHub (Jul 11, 2011):
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 commented on GitHub (Jul 11, 2011):
[ 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 commented on GitHub (Jul 11, 2011):
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 commented on GitHub (Jul 11, 2011):
you don't have to set up a channel to build and install a package.
@adeolemon commented on GitHub (Jul 11, 2011):
@till yes? :P
@till commented on GitHub (Jul 11, 2011):
@stof:
So assuming you guys would use pyrus to manage the required XML's etc..
Whenever you guys update and push, you do
pyrus makethis updates the include XMLs etc.. You commit those changes and push to github.Then, when I pull on my side I can use
pyrusorpearto install the code from github:Or:
Does that make sense?
@till commented on GitHub (Jul 11, 2011):
@jordi: ;-), I meant @seldaek.
@Seldaek commented on GitHub (Jul 13, 2011):
Pearhub is now fixed