Make Package.php optional
|Priority:||Could have||Due date:|
|Assignee:||Christian Jul Jensen||% Done:||
|Target version:||TYPO3 Flow Base Distribution - 2.0 beta 1|
Currently the required Package.php file is the only thing that differentiates native from non-native psr-0 compatible components (assuming packagestate is configured correctly).
Making the file optional and using it only if present, would simplify the packagemanager so there would be no need to have special handling of non-native components.
|related to TYPO3 Flow Base Distribution - Story #41031: Composer support for packaging||Resolved||2012-09-17|
Updated by Adrian Föder 12 months ago
+1, definitely. If the Package class is needed however for further processing (what I assume), the class maybe could be "generated" on the fly maybe (at least with
eval('class Foo...')), fed with information from the Meta XML.
Updated by Christian Jul Jensen 8 months ago
- Status changed from New to Under Review
Fixed by: https://review.typo3.org/#/c/14686/