Feature #37727

Make Package.php optional

Added by Christian Jul Jensen over 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Could have
Category:
Package
Start date:
2012-06-04
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
No
Complexity:
easy

Description

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 issues

Related to TYPO3 Flow Base Distribution - Story #41031: Composer support for packagingResolvedChristian Jul Jensen2012-09-17

Actions
#1

Updated by Adrian Föder over 9 years 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.

#2

Updated by Christian Jul Jensen almost 9 years ago

  • Status changed from New to Under Review
#3

Updated by Karsten Dambekalns almost 9 years ago

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

Also available in: Atom PDF