Summary: | mod_auth_pgsql needs new revision using apache-module.eclass | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Stewart (vericgar) (RETIRED) <vericgar> |
Component: | Current packages | Assignee: | PgSQL Bugs <pgsql-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | apache-bugs |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 76457 | ||
Attachments: | mod_auth_pgsql.patch |
Description
Michael Stewart (vericgar) (RETIRED)
2005-01-25 03:18:38 UTC
added ebuilds using apache-module.eclass the ebuild uses the eclass inappropriately, please see the attatched patch further it would be nice if mod_auth_pgsql ships a default config (example) Created attachment 52133 [details, diff]
mod_auth_pgsql.patch
thank you for your advise. But I'm not sure about this. In the apache herd's page( http://dev.gentoo.org/~vericgar/doc/apache-package-refresh.html ), APXS2_ARGS is defined in src_compile() function, but it's defined outside on yours. Which is better? the example makes use of the `use` function which should not be used in global scope, that's why it's placed in the function, but in mod_auth_pgsql there is no need to place it into local scope hollow has hit it right on the nose. The example in that documentation is showing a more complex package, that needs a custom APXSn_ARGS depending on whether the ssl USE-flag is set. If you don't have this complex case, then APXSn_ARGS should be defined globally for a cleaner ebuild. I recommend Hollow's patchs. He knows what he's doing :) ok. I thought there was another reason why it is declared in src_compile function. I've applied the patch and modified ebuild to install html documents which include example config file. Thanks! |