#253: installation: co-existence of several Invenio sites on the same box
-----------------------------+----------------------------------------------
Reporter: simko | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: *installation* | Version:
Resolution: | Keywords:
-----------------------------+----------------------------------------------
Comment (by simko):
Replying to [comment:1 rchyla]:
> The 2) link is not accessible (access denied)
The members of the mailing list should be able to access it. Just use
the email identity with which you are subscribed to the list.
(Due to the e-groups system used at CERN, the archives cannot be fully
open to anonymous guests. I planned put them onto gmane.org after
renaming the list (cdsware->invenio).)
> I generally miss the purpose of make/make install in the CMS system
> like Invenio -- it just makes things very complex and everything
> what make does can be done much more easier with python alone
We use autotools from the times Invenio had WML, Python, PHP, Common
Lisp. Now we have only Python and Common Lisp. We could indeed
abandon autotools more easily now and port the functionality to
something like SCons, but there are more urgent things to do. I don't
think the configure && make && make install process is that complex.
> (for instance, bin/* files have shebang which makes it tied to the
> configured python interpreter, where there could be just one entry
> point that simply executes the other bin applications, there is more
> of those, generally, if any file is there hardcoded in the source,
> it makes it non-portable).
Python interpreter is not hardcoded in the sources. The sources use
@PYTHON@ that is replaced by the wanted value from the --with-python
configure option. Usual autotools stuff.
--
Ticket URL: <http://invenio-software.org/ticket/253#comment:2>
Invenio <http://invenio-software.org>
