Bug #52984
closed
Epic #47018: Implement Composer support and clean package manager API
PackageManager resolving dependencies uses folderstructure for building keys
0%
Updated by Anja Leichsenring over 10 years ago
While testing #52828 I found a strange behaviour that was revealed by the patch.
My Structure inside doc root is as following:
drwxrws--- fileadmin lrwxrwxrwx index.php -> typo3_src/index.php lrwxrwxrwx typo3 -> typo3_src/typo3 drwxrws--- typo3conf lrwxrwxrwx typo3_src -> typo3conf/ext/050_core/typo3_src drwxrws--- typo3temp drwxrws--- uploads
This is done to have all files that go into version control inside typo3conf/ext and works fine until the moment. Inside typo3conf/ext/050_core/typo3_src are one or more core directories, the active one is pointed to by the symlink typo3_src.
If I now try to install an extension using the EM, I get a message like this:
The package "aboutmodules" depends on "050_coretypo3_srctypo3sysextcore" which is not present in the system.
The package key looked for but not found reflects the folder structure inside typo3conf/ext.
Updated by 
Updated by
Updated by Thomas Maroschik about 10 years ago
- Status changed from New to Rejected
Placing the typo3_src folder into typo3conf/ext is not good practice and shouldn't be supported. The ext folder has it's name from extension and means that only extensions should reside in this directory. I would advise to place the folder into typo3conf/src instead and everything should be fine.
If this doesn't reflect your opinion, please reopen the issue. :)