> Modified: trunk/fossology/INSTALL > =================================================================== > --- trunk/fossology/INSTALL 2009-07-08 17:05:11 UTC (rev 2318) > +++ trunk/fossology/INSTALL 2009-07-08 17:47:23 UTC (rev 2319) [snip] > @@ -103,8 +103,8 @@ > * For Debian nearly all packages can be found in main, unless you want > the non-free version of unrar > * For Ubuntu you will need a universe apt source setup > -* For RHEL you will need packages from EPEL > - http://fedoraproject.org/wiki/EPEL > +* For RHEL you can find needed packages from EPEL > + (http://fedoraproject.org/wiki/EPEL) or rpm.pbone.net.
Packages from the pbone are really hit or miss (and usually the latter). I'm not sure if recommending it is helpful. Ideally everything would be in EPEL, and I think we're getting closer to that with Jeff's work to get stuff in there. [snip] > -2.1.2.1 Service Dependencies > +2.1.2.1 - RHEL5 Dependencies > +---------------------------- > +For RHEL5, the breakdown of dependencies for complete functionality > +(build, install, run) is as follows: > + > +Packages to install from distro media > +------------------------------------- > +postgresql-8.1.11-1.el5_1.1 [snip] I thought we decided to put these "recipes" in the wiki? They are super useful, but the idea is to have the INSTALL doc not record specific versions if possible and have that info contained in the recipe docs. danger started a page to keep track of them all, but I can't find it (or a link to it). danger, Can you reply with the link and also with status of recipes? [snip] > +Packages not mentioned by fo-installdeps that were needed and found on rpm.p > bone.net > +------------------------------------- > +libextractor-devel-05.19a-1.el5 Jeff got this into fedora and it built for EPEL5 and should be available soon. He said that EPEL4 was harder, but he got it to work by disabling some gtk thumbnail thing so it should be available soon too. [snip] > -This script will help you finish the install, setting up things that > -can't be done by merely installing files on the filesystem. Because of > -the things it does, the script must be run as root. By default the > -script is designed to do everything you will need for a single machine > -install. If you are doing a multiple machine install, please see the > -INSTALL.multi document. > + > +Running this script to help finish the install is highly recommended, as > +it performs task that go beyond merely installing files on the filesystem. > +The script must be run as root. By default the script does everything you > +will need for a single machine install. If you are doing a multiple machine > +install, please see the INSTALL.multi document. I like my words better, but then I would wouldn't I :) [snip] > You are expected to already have a "postgres" user as part of the > system postgresql install, and a "www-data" user as part of the > -apache2 install. > +apache2 install. Note that some versions of Apache (like the one > +shipped with RHEL) use the user apache, not www-data. Whichever user > +your Apache uses, make sure that the user (www-data or apache) gets > +added to the fossy group. fo-postinstall does the right thing for distros that use apache, so this note is mostly not needed. If there are distros that don't use www-data or apache, then we'd still need to fix for that, but I think that corner case is not worth poluting the INSTALL doc. Thanks, -- Matt Taggart [email protected] _______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
