And I quote from the emerge output: * Ebuilds (like this one) that use the webapp-apache.eclass need to * be converted to use the new webapp.eclass, to be compatible with * webapp-config. * * Please file a bug on http://bugs.gentoo.org/, stating that this * ebuild needs converting to use the new approach. I couldn't find the bug already filed, so here it is.
(oops, way too high a priority - fixing now)
only the horde.eclass needs to be updated since all the horde packages use that i cant find any documentation on how webapp-config (no man page and the GLEP doesnt really do it) so someone else can touch up the eclass
webapp-config comes with 3 man pages - webapp.eclass(5) - webapp-config(5) - webapp-config(8) plus examples. I know that squirrelmail, trac, wordpress and phpmyadmin in the CVS tree all use webapp.eclass too. That should be enough to get you started ;-) Best regards, Stu
i was going by this: root@vapier 0 root # man webapp.eclass No manual entry for webapp.eclass root@vapier 0 root # man webapp-config No manual entry for webapp-config and the fact webapp.eclass isnt in cvs under the portage module i'll look into it then
Why would webapp.eclass be in CVS under the Portage module? My guess is that there are no man pages on your system because you haven't installed net-www/webapp-config yet. Best regards, Stu
*** Bug 51624 has been marked as a duplicate of this bug. ***
*** Bug 51625 has been marked as a duplicate of this bug. ***
*** Bug 51627 has been marked as a duplicate of this bug. ***
*** Bug 51629 has been marked as a duplicate of this bug. ***
*** Bug 51632 has been marked as a duplicate of this bug. ***
*** Bug 51635 has been marked as a duplicate of this bug. ***
*** Bug 51636 has been marked as a duplicate of this bug. ***
*** Bug 51637 has been marked as a duplicate of this bug. ***
*** Bug 51638 has been marked as a duplicate of this bug. ***
*** Bug 51639 has been marked as a duplicate of this bug. ***
Created attachment 32123 [details] horde.eclass stuart: take a look at this for me ?
webapps peeps: please see comment #16
Looks good. The only improvement I can suggest is to add a webapp_postinst doc to explain what to do after the package is emerged. This gets shown to users after webapp-config is used - even if they run webapp-config outside of Portage. Best regards, Stu
added to portage
Okay - this bug needs re-opening as SpanKY has removed this change from Portage. Best regards, Stu
and it wont get added back in until the webapp stuff goes stable :p
since 1.9 seems to be stable, i added it back in
