Hi! Please find attached horde.tar.gz containing horde-2.1.ebuild, Changelog and md5 digest. The Horde Framework is the glue that all Horde applications have in common. It is many things, including some coding standards, common code, and inter-application communication. The shared code provides common ways of handling things like preferences, permissions, browser detection, user help, and more. More details: http://www.horde.org I suggest net-www/horde or net-www/horde-base (because aditionals modules will become). Christophe GUILLOUX
Created attachment 2832 [details] horde-2.1.ebuild
Created attachment 2869 [details] horde-2.1.ebuild (attached gzip)
In general, we try very hard to avoid using pkg_postinst() and pkg_prerm() if at all possible. Is there any reason why they cannot be removed ? If you need to do configuration of your package that is at all intrusive (ie, you can envision one user in the world who would not like you to do it automatically), it should og into pkg_config and you should put out a notice in pkg_postinst() that the user must do ebuild <packagename> config for the package to configured.
Created attachment 4825 [details] horde-2.1.ebuild pkg_postinst() do not modify the system and pkg_prerm is removed.
Created attachment 5231 [details, diff] Ebuild patch This patch makes a few changes. 1. Allows us to change the HTTPD_USER and thereby change things like the HTTPD_GROUP, and HTTPD_ROOT. 2. Dies if HTTPD_ROOT is undefined. 3. Instead of installing horde as horde-2.1 and then making the user put a softlink in. I just had it install in $HTTPD_ROOT/horde 4. Changed the chown to make it owned by HTTPD_USER:HTTPD_GROUP rather than root:HTTPD_GROUP
Created attachment 5233 [details, diff] Ebuild Patch rev1 I forgot to change one of the paths listed to horde, instead of horde-2.1 This should obsolete attachment #5231 [details, diff]
Created attachment 5241 [details, diff] a configuration patch This adds a pkg_config with the recommended quick start from docs/INSTALL.
Fixed. Available for testing as net-www/horde-2.1. I don't know how to verify that this actually works nicely, so if any of you could give it a spin and reopen this bug if it fails, then I'd be very happy. If not, I'll assume it works. I'm going to continue with the rest of the horde packages later tonight.
It installs fine. Do you think we need the pkg_config thing? or not? I'm happy making the user read the INSTALL doc :)
