Task #42726

Document new package structure and management

Added by Christian Jul Jensen about 8 years ago. Updated almost 8 years ago.

Status:
Resolved
Priority:
Should have
Category:
- Documentation -
Start date:
2012-11-06
Due date:
% Done:

100%

Estimated time:
Sprint:
PHP Version:
Has patch:
No
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.

#1

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.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.
#2

Updated by Karsten Dambekalns almost 8 years ago

  • Assignee changed from Christian Jul Jensen to Karsten Dambekalns
#3

Updated by Gerrit Code Review almost 8 years ago

  • Status changed from New to Under Review

Patch set 3 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/16991

#4

Updated by Gerrit Code Review almost 8 years ago

Patch set 4 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/16991

#5

Updated by Karsten Dambekalns almost 8 years ago

  • Target version changed from 2.0 to 2.0 beta 1
#6

Updated by Karsten Dambekalns almost 8 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF