I installed Typo3 via the experimental ebuilds provided here in bugzilla. The app is devided in several parts: the core-part and an initial package to start your site, where you can choose from several alternatives. Because I don't want to provide other things on that vhost I installed the core-part containing only the sources to [vhost]/htdocs. Then I was not able to install the initial site also to [vhost]/htdocs because webapp-config complained about a previously installed package. But the source-package of Typo3 didn't install a single file to [vhost]/htdocs, everything went into [vhost]/typo3_src - awaiting an initial site to be installed later in [vhost]/htdocs. So i had to install the sources to [vhost]/htdocs/somedir only to keep my [vhost]/htdocs clean for the initial-site-package. [vhost]/htdocs/somedir is empty and exists only to keep the .webapp files. This works for me now but it isn't very straight forward. The behavior of the Typo3 ebuilds perfectly makes sense for this specific app, so I'm filing the bug for webapp-config. I can also imagine other webapps where you could want to install extensions, addons, etc. to the same dir as the base-app. A simple solution would be to just remove the "is the dir empty?"-check and let the user be responsible for not overwriting one app by another. But surely it would be better to have some kind of mechanism where the webapp-package-maintainer could allow only specific packages already to be installed in the target dir - other ones would lead to abort the install as it is implemented currently. But this would require a lot of work invested in webapp-config. Regards, S
I installed Typo3 via the experimental ebuilds provided here in bugzilla. The app is devided in several parts: the core-part and an initial package to start your site, where you can choose from several alternatives. Because I don't want to provide other things on that vhost I installed the core-part containing only the sources to [vhost]/htdocs. Then I was not able to install the initial site also to [vhost]/htdocs because webapp-config complained about a previously installed package. But the source-package of Typo3 didn't install a single file to [vhost]/htdocs, everything went into [vhost]/typo3_src - awaiting an initial site to be installed later in [vhost]/htdocs. So i had to install the sources to [vhost]/htdocs/somedir only to keep my [vhost]/htdocs clean for the initial-site-package. [vhost]/htdocs/somedir is empty and exists only to keep the .webapp files. This works for me now but it isn't very straight forward. The behavior of the Typo3 ebuilds perfectly makes sense for this specific app, so I'm filing the bug for webapp-config. I can also imagine other webapps where you could want to install extensions, addons, etc. to the same dir as the base-app. A simple solution would be to just remove the "is the dir empty?"-check and let the user be responsible for not overwriting one app by another. But surely it would be better to have some kind of mechanism where the webapp-package-maintainer could allow only specific packages already to be installed in the target dir - other ones would lead to abort the install as it is implemented currently. But this would require a lot of work invested in webapp-config. Regards, Sören Lorenz
It's a good point. Supporting this feature requires quite a bit of change to how webapp-config works internally. Rather than hack this into (the bash based) v1, I've added this to the TODO list for the python-based v2. There's no ETA on v2, sorry. Best regards, Stu
