| Summary: | zabbix-frontend doesn't install any files under /var/www/localhost/htdocs ??? | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | gentoo |
| Component: | New packages | Assignee: | Wolfram Schlich (RETIRED) <wschlich> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | karpi.web, norguhtar, shrdlu |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | All Ebuilds for ZABBIX include 1.1beta2 | ||
|
Description
gentoo
2005-08-16 12:09:04 UTC
(In reply to comment #0) > Not a bug per se. But just wondering why the zabbix-frontend ebuild doesn't > install any site files under /var/www/localhost/htdocs (similar to the cacti >and phpmyadmin ebuilds). Do we have to manually link the files under >/usr/share/zabbix ? No. Use webapp-config for install zabbix-frontend. > Actual Results: > Files get installed under /usr/share/webapps/zabbix-frontend/. Yes. It need for proper use webapp-config. Shouldn't the ebuild run webapp-config for you? We dont need to run it manually for things like cacti or phpmyadmin. (I have no idea how to use webapp-config and Im sure Im not the only one). (In reply to comment #2) > Shouldn't the ebuild run webapp-config for you? No >We dont need to run it manually for things like cacti or phpmyadmin. Really ? Compare this. part of cacti-0.8.6f-r1.ebuild: webapp_configfile ${MY_HTDOCSDIR}/include/config.php webapp_postinst_txt en ${FILESDIR}/postinstall-en.txt webapp_src_install part of zabbix-frontend-1.1_alpha7.ebuild: webapp_src_preinst cp -R php/* "${D}/${MY_HTDOCSDIR}" webapp_src_install I'm not found many differences. After install cacti you still need run webapp-config. >(I have no idea how to use webapp-config and Im sure Im not the only one). You can install and configure apache, but can't understand use webapp-config? Strange. You can run this command: webapp-config --help ? ;) (In reply to comment #3) > (In reply to comment #2) > > Shouldn't the ebuild run webapp-config for you? > No > >We dont need to run it manually for things like cacti or phpmyadmin. > Really ? Compare this. > > part of cacti-0.8.6f-r1.ebuild: > webapp_configfile ${MY_HTDOCSDIR}/include/config.php > webapp_postinst_txt en ${FILESDIR}/postinstall-en.txt > > webapp_src_install > > part of zabbix-frontend-1.1_alpha7.ebuild: > webapp_src_preinst > > cp -R php/* "${D}/${MY_HTDOCSDIR}" > > webapp_src_install > > I'm not found many differences. After install cacti you still need run > webapp-config. Yes. BUT THE POINT IS, one doesn't need to manually run webapp-config after installing cacti to use it. All the files are already under localhost. If you want to TRULY compare the ebuilds, install cacti yourself and you'll see what I mean. I realize its "hard" for you to see this from a user's point of view. > >(I have no idea how to use webapp-config and Im sure Im not the only one). > You can install and configure apache, but can't understand use webapp-config? Silly comment - no, you dont need to know webapp-config to install and use Apache. > Strange. You can run this command: webapp-config --help ? ;) Why bother installing from the ebuild if I can download and install the tarball myself? (I mean it will be less work for me than using the ebuild). I think you are missing the point: the ebuild should make things easier, not harder. (In reply to comment #4) > Yes. BUT THE POINT IS, one doesn't need to manually run webapp-config after installing cacti to use it. Really ? Ok. I'm install cacti step-by-step: step 1: #emerge info Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.3.5-20050130, glibc-2.3.5-r1, 2.6.13-gentoo i686) ================================================================= System uname: 2.6.13-gentoo i686 Intel(R) Pentium(R) 4 CPU 2.80GHz Gentoo Base System version 1.12.0_pre8 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.10 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-Os -mcpu=pentium4 -mmmx -msse -msse2 -mfpmath=sse -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" step 2: # emerge search ^apache$ Searching... e [ Results for search key : ^apache$ ] [ Applications found : 1 ] * net-www/apache Latest version available: 2.0.54-r14 Latest version installed: 1.3.33-r10 Size of downloaded files: 5,487 kB Homepage: http://httpd.apache.org/ Description: The Apache Web Server, Version 2.0.x License: Apache-2.0 step 3: #emerge search ^cacti$ Searching... u [ Results for search key : ^cacti$ ] [ Applications found : 1 ] * net-analyzer/cacti Latest version available: 0.8.6f-r1 Latest version installed: [ Not Installed ] Size of downloaded files: 1,055 kB Homepage: http://www.cacti.net/ Description: Cacti is a complete frontend to rrdtool License: GPL-2 step 4: #ls -l /var/www/localhost/htdocs/ total 20 drwxr-xr-x 9 root root 113 Dec 27 2004 ackerTodo -rw-r--r-- 1 root root 2326 Jul 13 10:26 apache_pb.gif -rw-r--r-- 1 root root 2414 Jul 13 10:26 apache_pb2.gif -rw-r--r-- 1 root root 1443 Jul 13 10:26 index.html -rw-r--r-- 1 root root 19 Apr 29 13:55 npadmin.pwd -rw-r--r-- 1 root root 18 Jul 14 11:42 test.php drwxr-xr-x 2 root root 38 Jul 14 11:43 zabbix step 5: # emerge cacti Calculating dependencies ...done! ... ... * * The 'vhosts' USE flag is switched ON * This means that Portage will not automatically run webapp-config to * complete the installation. * * To install cacti-0.8.6f-r1 into a virtual host, run the following command: * * webapp-config -I -h <host> -d cacti cacti 0.8.6f-r1 * * For more details, see the webapp-config(8) man page >>> Regenerating /etc/ld.so.cache... >>> net-analyzer/cacti-0.8.6f-r1 merged. >>> Recording net-analyzer/cacti in "world" favorites file... >>> clean: No packages selected for removal. >>> Auto-cleaning packages ... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. step 6: ls -l /var/www/localhost/htdocs/ total 20 drwxr-xr-x 9 root root 113 Dec 27 2004 ackerTodo -rw-r--r-- 1 root root 2326 Jul 13 10:26 apache_pb.gif -rw-r--r-- 1 root root 2414 Jul 13 10:26 apache_pb2.gif -rw-r--r-- 1 root root 1443 Jul 13 10:26 index.html -rw-r--r-- 1 root root 19 Apr 29 13:55 npadmin.pwd -rw-r--r-- 1 root root 18 Jul 14 11:42 test.php drwxr-xr-x 2 root root 38 Jul 14 11:43 zabbix > All the files are already under localhost. If you want to TRULY compare the ebuilds, install cacti yourself > and you'll see what I mean. I realize its "hard" for you to see this from a user's point of view. Simple question where my cacti ? Right answer you can view upper: * To install cacti-0.8.6f-r1 into a virtual host, run the following command: * * webapp-config -I -h <host> -d cacti cacti 0.8.6f-r1 * * For more details, see the webapp-config(8) man page > Silly comment - no, you dont need to know webapp-config to install and use Apache. But you need know webapp-config for install webapps in gentoo. > Why bother installing from the ebuild if I can download and install the tarball myself? (I mean it will be > less work for me than using the ebuild). I think you are missing the point: the ebuild should make > things easier, not harder. webapp-config is webapps manage tool. We can't know how you configure apache and your virtual hosts, but we can provide webapps manage tool, for easy manage installed webapps. Created attachment 71380 [details]
All Ebuilds for ZABBIX include 1.1beta2
I hope its useful.
I did not find it commands nowhere, so there it is: webapp-config -I -h localhost zabbix 1.1_alpha7 installs files into: /var/www/localhost/htdocs/zabbix/ (In reply to comment #7) > I did not find it commands nowhere, so there it is: > webapp-config -I -h localhost zabbix 1.1_alpha7 > > installs files into: > /var/www/localhost/htdocs/zabbix/ you need modify command webapp-config -I -h localhost -d zabbix zabbix 1.1_alpha7 (In reply to comment #7) > I did not find it commands nowhere, so there it is: > webapp-config -I -h localhost zabbix 1.1_alpha7 > > installs files into: > /var/www/localhost/htdocs/zabbix/ NO , sorry for my ignorance,, Ive send bad..:( Right is there: ls -l /usr/share/webapps/ ls -l /usr/share/webapps/zabbix-frontend/ webapp-config -I -h localhost -d zabbix zabbix-frontend 1.1_alpha7 sorry again.. (is there way to erase previous entry, plz ?) Install zabbix-frontend depends at USE flag vhosts. If vhosts enable frontend not install to /var/www/localhost/htdocs. If vhosts enable we need use webapp-config for proper install. May be add notice about this and close bug ? Taking this over from iggy. See bug #133230 (In reply to comment #10) > Install zabbix-frontend depends at USE flag vhosts. If vhosts enable frontend > not install to /var/www/localhost/htdocs. If vhosts enable we need use > webapp-config for proper install. May be add notice about this and close bug ? The point is that webapp-config should run automatically (installing the app under localhost) if the vhosts USE flag is not set, and not run but display a notice about how to install under a given virtual host if the vhosts USE flag is set. I don't know about zabbiz-frontend, but the monolithic zabbix ebuild (with USE=frontend) does NOT currently behave this way, while imho it should. |
