urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

web commit by http://id.loopysoft.com/matt/

master
Joey Hess 2008-01-20 18:59:51 -05:00
parent de8395367c
commit 3c4eb3a985
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/SharedHosting.mdwn
View File

@ -177,8 +177,8 @@ DreamHost has a pretty installation and management GUI for SVN, but it means you
# Why do I have to do all of this?
IANA Perl Expert. This is just what I found.
http://schwern.org/~schwern/talks/PREFIX/slides/slide001.html
[This appears to be a presentation outlining the problem](http://schwern.org/~schwern/talks/PREFIX/slides/slide001.html) -- Note, this site was up a few days ago, but appears to be down now. YMMV.
Part of the problem appears to be where modules decide to install themselves. Markdown, for example, installs itself to .../lib/perl5, which somehow never makes it's way into any of the INC paths used in the code. Not sure why, really. The rest of the modules seem to work well with the PREFIX option, but Markdown doesn't install to the path used from the PREFIX (hence the manual modification of Makefile.PL).
Part of the problem appears to be where modules decide to install themselves. Markdown, for example, installs itself to .../lib/perl5, which somehow never makes it's way into any of the INC paths used in the Perl. Not sure why, really. The rest of the modules seem to work well with the PREFIX option, but Markdown doesn't install to the path used from the PREFIX (hence the manual modification of Makefile.PL).
Basically, some stuff obeys the (apparently defunct and never really functional) PREFIX option, while the newer modules that use Module::Build, use the *install-base* option. It would be nice if Ikiwiki could handle being installed in a non-root situation, but I have no real suggestions on how to make that happen.