-
-
Notifications
You must be signed in to change notification settings - Fork 189
Feature/composer support #58
Feature/composer support #58
Conversation
Minor fix, setting correct library home page in composer.json.
|
Hey there are various issues regarding composer but it seems there is still no composer support. |
|
One of the few things in the PHP QA Toolchain not on Packagist yet. I look forward to it's arrival! |
|
@sebastianbergmann any chance to get this merged? There were no changes to the repo other than this one (obviously, as @mikedfunk said, the packagist hook is a must too :) ) |
|
BTW the PR is missing a doc update to |
|
@robocoder done |
|
👍 |
|
ping @sebastianbergmann Status on getting this merged in? |
|
@robocoder that code block is ok :) |
|
@Ocramius just trying to avoid an erroneous include btw can you follow this phploc convention of having a separate bin script for composer? https://github.com/sebastianbergmann/phploc/blob/master/composer/bin/phploc -- I think that would alleivate sebastian's concern as this would allow you to revert the change to phpcpd.php, and modify composer.json so composer users would have a vendor/bin/phpcpd (instead of vendor/bin/phpcpd.php). |
|
@robocoder if that helps bringing this in, well of course I will do it :) |
|
@sebastianbergmann now that the PR does not introduce changes to existing code, can we get this in? :) |
|
Does anyone have/know a maintained fork containing composer support which is available via packagist? |
|
That would just be wrong. Don't even think of doing it. @sebastianbergmann
|
|
I can accept and understand that sebastian has a lot todo but this is not a state we should keep, the issue is two months old and i dont see any reaction from sebastian side. |
|
@omares if you cannot wait for @sebastianbergmann then please use the "vcs" repository type as described in http://getcomposer.org/doc/04-schema.md#repositories and point it at |
|
Thank you Ocramius. |
|
For PHPUnit it makes sense to have different versions of PHPUnit on a per-project basis but I still fail to see the point of installing tools such as PHPCPD via Composer. I will eventually merge this pull request once I had the time to test it. However, this is of very low priority to me. |
|
It's just like "pushing a button"? I actually personally need this for a CI Marco Pivetta http://ocramius.github.com/ On 2 April 2013 16:18, Sebastian Bergmann [email protected] wrote:
|
|
Why not use the PHAR then? Just curious. |
|
Because I'd have to commit the phar to my repo (eww) or rely on the current Marco Pivetta http://ocramius.github.com/ On 2 April 2013 16:23, Sebastian Bergmann [email protected] wrote:
|
|
@sebastianbergmann yes, but there's better infrastructure to handle the downloads/dependencies in there.
As also @omares points out, committing a binary is kinda useless, and doesn't explain what is going on, while a diff does indeed show a change in the dependency constraints. And yes, it's the current standard way of doing things: I already have problems explaining my co-workers how to use composer. I don't want to mix up other ways of doing things when there's one "good-ish" one that makes things simpler :) |
|
👍 to get this on packagist. PHPCPD is a dependency to our development process. And dependencies has to be installable through the package manager. By the way: Its the last quality tool, which isn't on packagist yet. So, raise the priority @sebastianbergmann. |
|
I do not need stranger telling me how I should prioritize spending my free time, thank you very much. How about those who are interested in getting this pull request merged try it out and post here "yes, works for me" or "no, does not work for me"? That would speed up the process as with enough positive feedback I would not need to try it out myself. |
|
@sebastianbergmann Yes, it works for me. :) I've also verified the |
|
👍 Works perfectly for me :) |
|
Wow, that was fast. THANK YOU! |
|
Can you please test again after my recent changes? If all is well I'll roll a 1.4.1 release today or tomorrow. Thanks! |
|
@sebastianbergmann will do asap |
|
@sebastianbergmann looks good, nice improvement! Can you register the package on packagist and setup the hook? https://packagist.org/packages/submit |
|
I got an error caused by a static usage of I've got this error on @Ocramius's branch, too. |
|
@micha149 are you on 5.4? I just tried it on a 5.4 box and cannot reproduce with either phpcpd as requirement or as base repo. |
|
Oh, yes. I was. But after a switch to 5.3, I've got the same errors… The phpcpd script uses the right php executable. |
|
I'll look into it. |
|
@micha149 can you please provide your current |
|
Here is the composer json, which should not differ from sebatians repository: And here is the complete error: |
|
Please try with my latest patch. |
|
Yep. Now, it works great. Tested on 5.3.17 and 5.4.9 |
|
@sebastianbergmann Thanks for merging this PR. I can't find the project on packagist. Have you registered it and set up a hook yet? |
|
@tommygnr: Can you create a more "kept fresh one" than https://packagist.org/packages/shrink/phpcpd and test if it works? Also it might be worth to keep shrink in the loop. |
|
@hakre See what ocramius wrote in his description of this PR if you want to use a branch alias. |
|
@tommygnr: sorry to bother you, I did thought you were interested. I'm okay with the status-quo. comment deleted. |
|
For anybody following this thread phpcpd is now available on packagist. Thanks Sebastian |
|
Awesome! 👍 |
Fixes problem with executable in #53
To test it out:
Create a new directory and add following
composer.jsonfile to it{ "minimum-stability": "dev", "require": { "sebastian/phpcpd": "dev-feature/composer-support@dev" }, "repositories": [ { "type": "vcs", "url": "https://github.com/Ocramius/phpcpd.git" } ] }Run following:
curl -s https://getcomposer.org/installer | php php composer.phar installRun the cli tools:
should produce
Same works without defining the
composer.jsonfile and using the cloned repository instead.