Hope this is the right place for submissions. I wrote an ebuild for the tine20 groupware. Basically this ebuild should work with all branches/tags in http://git.tine20.org/git/tine20 just by renaming the ebuild. I have added them to my private overlay (https://github.com/matthid/gentoo-overlay/tree/master/www-apps/tine20) but I will add the files as attachment. Reproducible: Always Naming format: tine20-9999.ebuild -> master branch (live ebuild) tine20-2013.03.9999.ebuild -> 2013.03 branch ("stable branch") tine20-2013.03.8.ebuild -> 2013.03.8 TAG (official releases) Basically "tine20-2013.03.9999.ebuild" and "tine20-2013.03.8.ebuild" are only links to "tine20-9999.ebuild", and you can create additional links for other releases. missing things: - more database support (I'm only using mysql) - testing - emerge --config script for installing database & database user - distribute an apache vhost file (I have a working one if somebody want's to add this). I'm not quite sure how to tell the webapp-config program to install such a file.
Created attachment 359110 [details] main ebuild
Created attachment 359112 [details] config.inc.php
Created attachment 359114 [details, diff] memcached patch when enabled
Created attachment 359116 [details] postinstall message
Created attachment 359118 [details] a logrotate file for tine20
Created attachment 359182 [details] main ebuild file: tine20-9999.ebuild Some changes to add the MISSING keyword to the live ebuilds.