Document new package structure and management
- Package structure
help me make the docs better, please share your experences and wtf's in the comments.
Updated by Adrian Föder about 8 years ago
Documentation coverage wish:
I want to install an arbitrary package from "out there", for example TYPO3.SwiftMailer or guzzle.
TYPO3.SwiftMailer stands for a package which has compoer.json, but is not at packagist; guzzle stands for a fully packagist covered package.
- Is there an option to install these "on the fly", without being referenced from an "inquirer" json? (maybe via a
composer.pharcommand?) Is this even recommended?
- What's the best practice to include it else; I used to recommend people to add these requirements to their Package's json rather than their distribution json, because mostly their package requires something and not the distribution.