No you may notice the original request was for eprints 1 or 2, and the developers are now on version 3 and still going. I am not directly connected to the actual dev team but do a lot of the leg work. Eprints 3 works with apache2 and simply adds a config file to sites-available (which users enable when they have configured their install).
Not really, the developers picked perl as the language they wanted to code the package in and they have coded it in a modular way but there is no real benefit in haveing the modules packaged independently as they all require the eprints package anyway. There may be a possibility of having eprints-plugin-foo in the future as there are plugins available separately via the official package website. The package itself does depend upon a few perl modules being already installed to work and I have include these in the dependancies.
The coders of this package are possibly more experienced than the person who originally posted to ITP and the installation process has improved. There are just a lot of dependancies which tend to scare people (especially redhat users). If you take a brief look at the rules file and post install scripts i think you will find that it isn't that complex.
I appreciate any advice you can offer on this package and anything which I need to work on in order to get it accepted into the package tree. Thanks in advance. ----------------------------------------------------------- David Tarrant EPrints Debian Maintainer School of Electronics and Computer Science University of Southampton Southampton SO17 1BJ UK ----- www.ecs.soton.ac.uk www.eprints.org ----------------------------------------------------------- |