To all,

Now that I have FOSSology up and running, I wanted to share my 
installation experiences - Hopefully this will be helpful to someone else 
(or can help augment the installation instructions)

And of course a big THANK YOU to the FOSSology team for helping me work 
thru the various problems I encountered ..


FOSSology installation

I will first start by saying its been a LONG time since I used Unix/Linux 
- So its taking a bit of time to get up to speed with some of the 
commands.     First, I would say that trying to get FOSSology installed on 
Redhat 4.x takes a little more expertise than I have at the moment - and 
once I started running into issues around upgrading specific components 
(and the messages generated) - I realized that it would be more 
advantageous to find a 5.x environment

Specific to 5.x - I was able to get a spare developer grade workstation.  
Overall, I found the installation documentation (at 
http://fossology.org/rhel5_1.1) to be very helpful  -  I did encounter a 
few instances where I needed to install additional files:


1.   Libextractor reported a dependency of   libucl.so.1 -  which I found 
at

http://rpm.pbone.net/index.php3/stat/4/idpl/11438442/com/libtool-ltdl-1.5.22-6.1.i386.rpm.html

2.  Sleuthkit reported a dependency on a Perl Date Library -  the file was 
on the Redhat distro at -   perl-DateManip-5.44-1.2.1.noarch

3.  For reference, you need to install the UCL package prior to UPX (UPX 
depends on UCL)

4.  What I also learned is how to check if packages are installed - The 
way to do that:

# rpm -qa php 
php-5.1.6-23.2.el5_3 
# rpm -qa perl 
perl-5.8.8-27.el5 
# rpm -qa httpd 
httpd-2.2.3-31.el5 
# rpm -qa php 
php-5.1.6-23.2.el5_3 
rpm -qa postgres 
postgresql.i386 0:8.1.18-2.el5_4.1 


5.  When it comes to installing FOSSology install itself, I HIGHLY 
recommend using YUM - it resolves a number of additional dependency files 
(but does so automagically ..)  - If you have a firewall, you may need 
some assistance in modifying a file called yum.conf to talk to the 
appropriate proxy ..


6.   Post FOSSology install

After you install FOSSology - some post installation "checks" you should 
consider:

A . Go to  /var/local/lib/fossology/agents   - VERIFY that   License.bsam  
exists

               If License.bsam does NOT exist  (You can get into 
FOSSology, but it won't do much and will generate log file errors)

              i.    Verify that all prerequisite files have been installed
             ii.    Try running  fo-postinstall  located in 
/usr/lib/fossoslogy  (this should build License.bsam)


B.  Make sure to make the various configuration changes specified in  (
http://fossology.org/rhel5_1.1)


C.  Start  the scheduler :

                /etc/init.d/fossology start  (detailed at  
http://fossology.svn.sourceforge.net/viewvc/fossology/trunk/fossology/INSTALL
)


D.  Once FOSSology is installed, make sure that the underlying services 
will get started on the next reboot - Service status we make changes to 
included:

Apache Web Server
Tomcat
Postgres
_______________________________________________
fossology mailing list
[email protected]
http://fossology.org/mailman/listinfo/fossology

Reply via email to