Task #42726: Document new package structure and management - TYPO3.Flow - TYPO3 Forge

Task #42726

Status:

Resolved

Start date:

2012-11-06

Priority:

Should have

Due date:

Assigned To:

% Done:

100%

Category:

- Documentation -

Target version:

Sprint:

Has patch:

PHP Version:

Complexity:

Description

Topics

- Composer
- Package structure
- Upgrading
- Installing
- Maintaining

help me make the docs better, please share your experences and wtf's in the comments.

[TASK] Update Package Management section

This adjusts the package management section of the TYPO3 Flow Guide to
the composer changes.

Change-Id: I7772051938a4306328108bacde34710c54fc3a69
Resolves: #42726
Releases: 1.2

[TASK] Adjust suggested folder structure in Package Management section

I7772051938a4306328108bacde34710c54fc3a69 introduced suggested
names for directories under Resources/Public.

This adjusts the suggested folder names as discussed and adds a link
to the ResourceManagement chapter.

Change-Id: I0986699fb770dda58dae3daa9fae434b37088dee
Related: #42726
Resolves: #13694
Releases: master, 2.0

[TASK] Adjust suggested folder structure in Package Management section

I7772051938a4306328108bacde34710c54fc3a69 introduced suggested
names for directories under Resources/Public.

This adjusts the suggested folder names as discussed and adds a link
to the ResourceManagement chapter.

Change-Id: I0986699fb770dda58dae3daa9fae434b37088dee
Related: #42726
Resolves: #13694
Releases: master, 2.0

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.phar command?) 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.