I can't believe i'm posting a bug to my own ebuild, but the dev who submitted it changed the way it determines the destination directory, such that you can no longer specify on the command line where the web files are to go. What if you want it in a virtual server's directory? What if you want it in a different install of apache? That is why I had the [ -z ${HTTPD_DOCROOT ] etc lines... the ebuild only chooses location if the user does not specify. I was going to wait for the apache eclass and use that in conjunction with my method above, but /etc/passwd would do... AS LONG AS THE USER CAN SPECIFY OTHER. Reproducible: Always Steps to Reproduce:
Currently apache is setup so you can create the apache user before emerging and set a different directy as it's homedir, thus altering the default datadir when apache is actually installed. Say, for instance, someone creates the apache user and sets its homedir to /some/diff/path. Then they emerge zoneminder which drags in apache as a dep. Apache is smart enough to recognize the homedir and use that as the custom datadir, however your original zoneminder ebuild would not have been aware of that change.. forcing the user to set a completely seperate env variable. While that doesn't seem that complicated, the user would have no idea that that needs to be done unless they were to read the ebuild. You're correct, that the apache eclass would be helpful, but for the moment the only way is to use the same method as apache. In all honesty, making the changes I did didn't remove any functionality. If you want to use a different location for zoneminder you can alter the apache users homedir and you'll get the same results. I would like to stay away from having to set multiple, extra, hidden env vars to solve this. Perhaps one var that can be mentioned in pkg_postinst() to the user on how to set it. So what's your best solution with all things considered? Also, as an experienced hothead I can promise you a cooler tone in your bug reports will get more results.
Video folks, This sounds like an interesting app. Please take a look; if you could get it to compile/work, that would be great. I can do the webapp.eclass magic once it works. Best,
I would like to use zoneminder, but I am interested in using some of the features that are only available after version 1.19 - particularly, capturing motion jpeg streams. If someone could help put together an ebuild for a more recent version of zoneminder, I would be more than willing to test it.
I'd like to check on where we are with this bug. It appears that Matt was the intial submitter, and that the webapps herd has offered to help in getting this setup with the webapps eclass. I'd do it myself, but I'm not that familiar with the webapps eclass to want to alter this ebuild any. Thanks ahead of time for your responses and thank you for using Gentoo!
Err... WTF is zoneminder doing installing files in /home/httpd??? There seems to be a lack of policy direction here.
I'm confused here. For one, the package maintainer claims he used apache's homedir (which is by default set to /home/httpd) to install - which makes zero sense, since Gentoo doesn't use the homedir itself when installing the apache content; that always goes in /var/www/localhost. Next, one of the apache guys claims they'd do it differently if and when portage would provide a better way. These things seem to contradict eachother. One of two things needs to happen: 1) build a required/preset var into apache ebuild designating the path of the documentroot installation - defaulting to /var/www or whatever, or 2) require apache-dependent content packages (like zoneminder) to query the apache install and get the install directory right the first time. Neither would be that hard, but the first one is cleaner across the board.
*** Bug 92585 has been marked as a duplicate of this bug. ***
Surely it should simply use webapp.eclass, and have a vhosts USE flag?
Folks, 1.21.2 is in CVS, please test
