I would like this taken into portage. I think it fits in app-admin, but I don't really know. Reproducible: Always Steps to Reproduce: 1.Ebuild digest 2.ebuild unpack 3.emerge <testing> Actual Results: I got a complete package
Created attachment 36775 [details] Argus 3.3 ebuild
Created attachment 36776 [details] argus 3.3 makefile patch [allow for sandbox]
Created attachment 36777 [details] Argus 3.3 init script.
I have not done extensive testing yet. Apache integration is still broken. It builds and installs though. I will upload more files later.
Created attachment 36837 [details] Fixed version of the init script. d'oh - the first one did not even try to work.
did you test it on sparc or x86? anyway, a new ebuild should be ~arch for all the archs first.
Created attachment 37608 [details] updated argus ebuild. Updated ~x86, remove all untested archs.
Created attachment 37618 [details] argus-3.3.ebuild - Fixed Ebuild Updated ebuild: remove untested arch's, change KEYWORDS to ~x86 Add apache to dependancies. ** Any cgi-capable server will do. (fix)? Automatically place arguscgi in /var/www/localhost/cgi-bin
webapps are supposed to use the webapp.class. see webapp-config and webapp.eclass(5).
When will this make it into portage?
Someone needs to get this organized with the webapp class. Further more, I just installed this on a new box about a week ago. Somehow it has gotten bit-rot in four short months. All of the argus libraries had an incorrect path, etc. Mod_perl usage is apparently also b0rked, however, once you fix the paths it runs well in CGI mode. The argus daemon also runs pretty well. So in short: a. Fix path problems in argus when installing via ebuild. b. fix ebuild to use the webapp class c. maybe tshoot mod_perl and figure out why that is borked. I have purposefully avoided working on it because I beleive that there is about to be another release.
If someone wants to post a fixed argus ebuild I've got a system I'd like to test it on, preferably in a tarball so I can inject it into portage. Perhaps he's going to release a new version but I doubt that it's going to be archetecturally much different than the current one.
Created attachment 49969 [details] Tarball of the current argus portage directory This ebuild seems to work, but does not include any of the webapp stuff yet. I would greatly appreciate any/all testing, and bugfixes against this. The changes made were minor, and much of it was simply creating the directory structure.
Created attachment 50187 [details] This ebuild fixes the perl path issue and adds needed directories to /usr/share/argus this is sick+wrong but best I can tell it works. This ebuild fixes the perl issues, and adds missing dirs in /usr/share. Includes all previous fixes including a flag for ssl support.
Created attachment 50652 [details] Argus Ebuild Final fixes noncreated directores fixes install does not include css/images/siren fixes arguscgi goes to wrong path in /var this ebuild is now stable and working on my system, I think it's ready to be committed as ~x86.
Created attachment 53486 [details] argus ebuild this ebuild includes all previous fixes and webapp.eclass support
Created attachment 54302 [details] argus ebuild passes repoman full
hi guys. there is an ebuild for mod_perl-2.0.1 in portage now. this may solve some of your problems. there has been some changes to module names with mod_perl-2.0.1 so it might not help until Argus is updated to the new layout. but please give it a test with the new version and see if it helps.
(In reply to comment #18) > hi guys. > there is an ebuild for mod_perl-2.0.1 in portage now. > this may solve some of your problems. > there has been some changes to module names with mod_perl-2.0.1 so it might not > help until Argus is updated to the new layout. > but please give it a test with the new version and see if it helps. I've got an ebuild rev'd to 3.4 and a clean system to test it on, I'm going to set it up and I'll make sure it doesn't have bit rot and then commit it this weekend.
Please reopen with your new ebuilds attached
