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

[BUG] the http://composer.lightwerk.com/packages.json should contain "replace" with the extension keys #8

Open
AndreasA opened this issue Oct 6, 2014 · 2 comments

Comments

@AndreasA
Copy link

AndreasA commented Oct 6, 2014

Hi,

it is necessary to add replace with extension keys for extensions and typo3 for "typo3/cms" to the package.json to satisfy composer requirements.

In typo3 6.2 it is possible to completely define requirements for typo3-cms via composer which means extension keys for extensions but in order to use the typo3-ter extensions / typo3-cms from lightwerk repository via composer this only works if those packages also use "replace".

I cannot use typo3-ter/ as requirement because typo3-cms would then want typo3ter.key to be installed.
For typo3 it is possible to specify via typo3 or also typo3/cms-core . However, by using typo3/cms-core composer loads the typo3-cms-installers which completely disable the lightwerk installers and therefore all typo3-ter extensions are installed wrongly.

@AndreasA
Copy link
Author

AndreasA commented Oct 6, 2014

And if the extension has a composer.json then one would also need to add the replace for the composer name of the extension, after all I could have added that one to require too.

@AndreasA
Copy link
Author

AndreasA commented Oct 6, 2014

Maybe you also should change the "type" for extensions and the core to reflect what typo3 uses with 6.2
extensions: "typo3-cms-extension" and core "typo3-cms-core"

That way the installation would still work if instead of your installers the typo3-cms-installers were used or the composer/installers.

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