It doesn't make much sense to do a *dev* install from stable. Do your dev install from a git clone.
Just follow the instructions in INSTALL.debian. When it asks you for a separate place to put config files (default ~/koha-dev/) that's where your real config ends up, like: ~/koha-dev/etc/koha-httpd.conf Don't tell it to put it on top of the template file (or inside your kohaclone dir), that would be weird. You still have to do perl Makefile.PL; make; make install; # of course. -- Joe Atzberger LibLime - Open Source Library Solutions On Thu, Jul 16, 2009 at 3:43 PM, Library Guy <library.guy.z...@gmail.com>wrote: > perl Makefile.PL creates a complete Makefile when run from the stable tar, > but if instead I choose a dev install from kohaclone after git pull, > the Makefile is > incomplete. Hence my dev version of koha-httpd.conf contains only > variable names: > > ## OPAC > <VirtualHost __WEBSERVER_IP__:__WEBSERVER_PORT__> > ServerAdmin __WEBMASTER_EMAIL__ > DocumentRoot __OPAC_WWW_DIR__ > ServerName __WEBSERVER_HOST__ > # ServerAlias opac.mydomain.com > ScriptAlias /cgi-bin/koha/ "__OPAC_CGI_DIR__/opac/" > ScriptAlias /index.html "__OPAC_CGI_DIR__/opac/opac-main.pl" > ScriptAlias /opac-search.pl "__OPAC_CGI_DIR__/opac/search" > ScriptAlias /search "__OPAC_CGI_DIR__/opac/search" > ErrorLog __LOG_DIR__/koha-opac-error_log > # TransferLog __LOG_DIR__/koha-opac-access_log > SetEnv KOHA_CONF "__KOHA_CONF_DIR__/koha-conf.xml" > SetEnv PERL5LIB "__PERL_MODULE_DIR__" > > What am I missing? >
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
