Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require composer-installers to give us a possibility to use it #72

Closed
OnkelTem opened this issue Aug 21, 2017 · 1 comment
Closed

Require composer-installers to give us a possibility to use it #72

OnkelTem opened this issue Aug 21, 2017 · 1 comment

Comments

@OnkelTem
Copy link

Currently your composer.json restricts ability to install it somewhere under website's root - instead it goes to vendor/ which makes no sense as vendor/ is not exposed to direct invocation and is located above the website's root.

Please add:

    "require": {
        "composer/installers": "~1.0"
    }

to let us install the library to specified locations using standard means:

{
    "extra": {
        "installer-paths": {
            "sites/all/libraries/{$name}": ["ckeditor/ckeditor"]
        }
    }
}

See: https://getcomposer.org/doc/faqs/how-do-i-install-a-package-to-a-custom-path-for-my-framework.md

@OnkelTem
Copy link
Author

OnkelTem commented Aug 22, 2017

Sorry, ignore this issue. You won't get stuff going to some custom directory only by providing the dependency from composer/installers. As a matter of fact you don't need such a dependency. What you really need is oomphinc/composer-installers-extender composer plugin
which allows for custom installation paths of composer packages:

$ composer require oomphinc/composer-installers-extender

then add this to the extra section of your composer.json:

  "extra": {
    "installer-types": [ "library" ],
    "installer-paths": {
      "path/to/custom/installation/path{$name}": [
        "ckeditor/ckeditor"
      ],
  }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant