[horde] cvs ... and then-- SOLVED

[w trillich]

Martin Lohmeier wrote:
> w trillich wrote:
>>(and which document mentions that ever-so-crucial "cd" 
>>command?)
> 
> <your-module>/docs/INSTALL ;-)

um... we scoured those multiple times, and-- aha. thanks.

we had created our own "horde" directory to download all this 
stuff into. confused things a bit. plus, ...

from imp/docs/INSTALL:
=====
IMP is written in PHP, and must be installed in a web-accessible 
directory. The precise location of this directory will differ 
from system to system. Conventionally, IMP is installed directly 
underneath Horde in the web server's document tree.

Since IMP is written in PHP, there is no compilation necessary; 
simply expand the distribution where you want it to reside and 
rename the root directory of the distribution to whatever you 
wish to appear in the URL.  For example, with the Apache web 
server's default document root of ``/usr/local/apache/htdocs``,
you would type::

    cd /usr/local/apache/htdocs/horde
    tar zxvf /path/to/imp-x.y.z.tar.gz
    mv imp-x.y.z imp
=====

so: "conventionally, we put it under horde. simply expand it 
where you want it." wow. yes, it's in there, as a suggestion to 
follow tradition, but it's also rooted right back out again.

so it appears that if we don't follow that convention, it's 
broken, so we should use a stronger word than 'conventionally' 
perhaps.

even the path from the 'cd' example doesn't explicitly state 
that the final component is actually anything specific other 
than a directory for apache to sling html/php from.

for example, in debian, we use /var/www and in our particular 
case we're using /var/www/horde.domain.tld so the sample path 
seems to be either a sample or a suggestion, as if an url like 
http://domain.tld/horde would be the url to get to the horde 
modules... until--


from horde/docs/INSTALL:
=====
4. Extract tarball::

      cd /usr/local/apache/htdocs
      tar zxvf /path/to/horde-x.y.z.tar.gz
      mv horde-x.y.z horde
=====

so, taken together, those two 'cd' snippets imply that imp might 
work as a subdir under the horde dir. it'd help (folks like us) 
if that was spelled out in more detail -- something like this:

	note that 'horde' is the mac daddy library gizmo;
	all the actual modules (imp, kronolith, nmeno, etc)
	depend on it and should reside in subdirectories of
	the horde 'module' install.

	.../horde
	.../horde/imp
	.../horde/gollem
	.../horde/framework <= even 'framework' goes under horde
	.../horde/nag

bad idea?

also the INSTALL docs were talking about the tarball, and we 
were installing from cvs instead; we [mistakenly] presumed that 
cvs would have the hierarchy ready-to-go. or that there would 
otherwise be a "make install" construct to get the files to the 
proper position within the webserver docroot.

i hope we weren't the only ones confused by this. sure, now that 
we're familiar with the hierarchy, we won't make that mistake 
again. but the next newbie probably will.

====

so. now that the hierarchy is set up, things are looking much 
better. except imp won't connect -- new thread soon.