On Sep 26, 2009, at 6:20 PM, Marc G. Fournier wrote:

First, I just ran git clone and most seems to go perfectly ... I'm doing
this on a new site though, as looking at the DB schema, there are a bunch
of changes in there that make me a wee bit nervous about doing an upgrade

There is a *slight* difference in Bundle/Slash.pm from what is in CPAN ...
*very* minor, but you'll want to make sure you install the one from git

Now, the 'make; make install' phase does break though ...

cp -r themes/* /usr/local/slash/themes
# Ensure we use the proper Perl interpreter and prefix in all scripts that
# we install. Note the use of Perl as opposed to dirname(1) and
# which may or may not exist on any given system.
(replacewith=`perl -MConfig -e 'print quotemeta($Config{startperl})' | sed
's/@/\\@/g'`;  binfiles=`find bin -name CVS -prune -o -name .git -prune -o
-name [a-zA-Z]\* -type f -print`;  sbinfiles=`find sbin -name CVS -prune
-o -name .git -prune -o -name [a-zA-Z]\* -type f -print`;
themefiles=`find themes -name CVS -prune -o -name .git -prune -o -name
[a-zA-z]\*.pl -print`;  pluginfiles=`find plugins themes/*/plugins -name
CVS -prune -o -name .git -prune -o -name [a-zA-Z]\*.pl -print`;
tagboxfiles=`find tagboxes themes/*/tagboxes -name CVS -prune -o -name
.git -prune -o -name [a-zA-Z]\*.pl -print`;  if [ "$replacewith" !=
"\#\!\/usr\/bin\/perl" ]; then  replace=1;  replacestr='(using perl)';
else  replace=0;  fi;  for f in $binfiles $sbinfiles $themefiles
$pluginfiles $tagboxfiles; do  n=/usr/local/slash/$f;  install -d
/usr/local/slash/$d;  if [ $replace ]; then  cat $f |  sed -e
"1s/\#\!\/usr\/bin\/perl/$replacewith/" > $n.tmp;  install -m 0755 $n.tmp
$n;  rm -f $n.tmp;  else  install $f $n;  fi;  done)
find: themes/*/plugins: No such file or directory

And that is where it ends ...

The problem *appears* to be with:

PLUGINFILES = `find plugins themes/*/plugins -name CVS -prune -o -name
.git -prune -o -name [a-zA-Z]\*.pl -print`
TAGBOXFILES = `find tagboxes themes/*/tagboxes -name CVS -prune -o -name
.git -prune -o -name [a-zA-Z]\*.pl -print`

there are no themes/*/{plugins,tagboxes} directories, so the find itself
fails ... removing that from the find path fixes that, am assuming that if
the slashdot theme was there, that is where it would have picked it up
from ... ?

You don't mention what version you are attempting to *upgrade from*.

I'm assuming you are trying to upgrade from 2.2.6 tarball to git master "head".

If that's the case, you won't be able to just clone the git repo and make install. First you'd have follow all the upgrade instructions (which alters your DB's structure et all). *Then* you'd make install w/ the newer code.

2.2.6 should have a themes directory and atleast one theme in it (slashcode).
but you're correct, 2.2.6 certainly doesn't have the tag* plugins, users2, a number of plugins that have been created since 2.2.6. however, tagboxes is an "odd" plugin the way it is layed out, if I recall correctly.