summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2008-01-20 18:59:51 -0500
committerJoey Hess <joey@kitenet.net>2008-01-20 18:59:51 -0500
commit3c4eb3a985f91e42620f248ef6c9bb5aab842e89 (patch)
tree1aeb29c73f1a8c30602884c9ae582859258c8712
parentde8395367c6e8b70a45c25e3ae190fd89018c34a (diff)
web commit by http://id.loopysoft.com/matt/
-rw-r--r--doc/SharedHosting.mdwn4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/SharedHosting.mdwn b/doc/SharedHosting.mdwn
index 46c63202c..cc39e7099 100644
--- a/doc/SharedHosting.mdwn
+++ b/doc/SharedHosting.mdwn
@@ -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.