Closed ddebernardy closed 10 years ago
You are welcome, actually I'm working on that right now! :) and I'll rename it as well
how about mnabil/composer-install-anywhere
for a name?
And if I may, please change those namespaces and class names to something more sane too, e.g.:
namespace MNabil\Composer\InstallAnywhere; // or whatever seems logical
use Composer\Installer\LibraryInstaller as BaseLibraryInstaller;
class LibraryInstaller extends BaseLibraryInstaller { ...
how about mnabil\composer-custom-directory-installer
for the package name?
and for the namespace, I'll take that in considerate and get back to you, because composer itself got confused, let me run some tests and get back to you.
okay, I ran some tests, I confirm there are no conflicts or anything.
here is the namespace I used Composer\CustomDirectoryInstaller
?
so, what do you think? I guess it is better and more declarative than before.
much better, yeah.
okay .. gr8, I'll commit the changes right now :)
thank you very much for the suggestions
Thank you for writing this. Mind adding it to packagist.org? (Perhaps after renaming it to something more sane, e.g.
"mnabil/composer-installer-plugin"
?)