On Tue, 12 Apr 2011, Roman Chyla wrote: > We should really create some sommunity github for Invenio goodies > where we could keep things like that?
As I have expressed in the past, my take on this topic is that it is useful to have some tiny official working script examples -- and we do have those -- because tiny scripts are easy to understand and adapt. People could read them and adapt them to their needs. I don't think it would be advantageous to maintain a huge community wide script that would tackle all the operating systems and all the people's preferences (eggs vs debs) in a one-size-fits-all manner. Such a thing would be hard to follow and would not suit all the personal tastes anyway. As the Unix saying goes, if you perform a certain operation three or four times, chances are you may repeat it the future too, so you should write a script. Every developer has probably his/her own habits in this domain and these habits are best served by taking an inspiration from an existing official tiny recipe examples and adapting these recipes to suit his/her needs. So example scripts belongs more in the domain of people's personal repositories (or even to wikis, if they are tiny) than in some official or community repository that would still not fit all the personal preferences and scenarios. Personal repositories do the job nicely here, I think. (E.g. I have a few scripts that do useful stuff like check kwalitee changes between branches, check I18N files, etc. It may be perhaps useful if I publish them somewhere in my personal space, but probably not in the official repository. I had planned to plug them into Bitten green/red light thingy, but this would be even better done after we do some more Monday cleanup sprints... but I'll digress, I'll sent a separate message about this.) > I was recently in need to install Invenio on a bare SLC5 machine. > Daunting perspective... I discovered the Quattor profile, but quickly > gave up after skimming through the installation instructions (so > complex, they cannot be serious!) In the case of a barefoot SLC5, you can install prerequisites by doing: | yum install MySQL-python PyXML alsa-lib apr apr-devel apr-util \ | apr-util-devel cyrus-sasl-devel db4-devel distcache epydoc \ | expat-devel freetype-devel gettext-devel gpm httpd libXtst \ | libart_lgpl libgcj libgcrypt-devel libgpg-error-devel \ | libjpeg-devel libxslt libxslt-devel libxslt-python lynx mod_ssl \ | mod_wsgi mx mysql mysql-devel mysql-server numpy openldap-devel \ | perl-DBD-MySQL postgresql-libs python-devel python-setuptools \ | python-wsgiref screen vim-enhanced w3m git pylint python-dateutil \ | python-simplejson | | rpm -Uvh http://swrep/swrep/x86_64_slc5/MySQL-python-1.2.2-1.slc5.x86_64.rpm | rpm -Uvh http://swrep/swrep/x86_64_slc5/hashlib-20081119-1.slc5.x86_64.rpm | rpm -Uvh http://swrep/swrep/x86_64_slc5/mechanize-0.1.11-1.slc5.noarch.rpm | rpm -Uvh http://swrep/swrep/x86_64_slc5/ClientForm-0.2.10-1.slc5.noarch.rpm | | wget http://packages.sw.be/pdftk/pdftk-1.41-1.el5.rf.x86_64.rpm | rpm -ivh pdftk-1.41-1.el5.rf.x86_64.rpm I don't think it should be necessary to script around this yum one-liner plus few additional RPM packages from Quattor? Once this is done, you can follow the usual guide: <https://twiki.cern.ch/twiki/bin/view/CDS/InvenioInstallationSLC5> I'll try to document the barefoot-SLC5 vs Quattorised-SLC5 use case better when I'll be moving the corresponding TWiki page to Trac. Best regards -- Tibor Simko
