From f5466ad7173459bc9481781d8f54ba969f56a516 Mon Sep 17 00:00:00 2001 From: Jon Dowland Date: Fri, 23 Apr 2010 16:29:05 +0100 Subject: how important is perl 5.10? --- doc/setup/discussion.mdwn | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'doc/setup') diff --git a/doc/setup/discussion.mdwn b/doc/setup/discussion.mdwn index b71263dae..2000c5dfb 100644 --- a/doc/setup/discussion.mdwn +++ b/doc/setup/discussion.mdwn @@ -245,3 +245,12 @@ Thank you! I'm not a Perl programmer, so what's your opinion: is this behavior a I am experiencing the same problem "/etc/ikiwiki/custom: failed to set up the repository with ikiwiki-makerepo " on Debian squeeze with perl5.10.0. Upgrading to ikiwiki 3.10 fixes it. -- [Albert](http://www.docunext.com/) + +---- + +Just a note, perl 5.10 isn't packaged as part of RHEL or thus CentOS nor EPEL, +so it's not especially trivial to satisfy that requirement for ikiwiki on +those platforms, without backporting it from Fedora or building from source. +However, I have an ikiwiki 3.20100403 running on RHEL-4 supplied 5.8.8 without +(seemingly too much) complaint. How strong is the 5.10 requirement? what +precicely breaks without it? -- [[Jon]] -- cgit v1.2.3 From 796ece2a8a482f219a5d4c568af271286511574e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 23 Apr 2010 13:30:52 -0400 Subject: response --- doc/setup/discussion.mdwn | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'doc/setup') diff --git a/doc/setup/discussion.mdwn b/doc/setup/discussion.mdwn index 2000c5dfb..74f7740db 100644 --- a/doc/setup/discussion.mdwn +++ b/doc/setup/discussion.mdwn @@ -254,3 +254,7 @@ those platforms, without backporting it from Fedora or building from source. However, I have an ikiwiki 3.20100403 running on RHEL-4 supplied 5.8.8 without (seemingly too much) complaint. How strong is the 5.10 requirement? what precicely breaks without it? -- [[Jon]] + +> I don't remember what was the specific problem with perl 5.8.8. All I can +> find is some taint checking bugs, which are currently worked around by +> taint checking being disabled. --[[Joey]] -- cgit v1.2.3 From 651acf8b1490ebdfe15c11fde3792c13fb118f31 Mon Sep 17 00:00:00 2001 From: "http://jeremiahfoster.com/" Date: Wed, 9 Jun 2010 11:55:11 +0000 Subject: Started discussion --- doc/setup/byhand/discussion.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/setup/byhand/discussion.mdwn (limited to 'doc/setup') diff --git a/doc/setup/byhand/discussion.mdwn b/doc/setup/byhand/discussion.mdwn new file mode 100644 index 000000000..97ae40438 --- /dev/null +++ b/doc/setup/byhand/discussion.mdwn @@ -0,0 +1 @@ +What directory is the 'working copy'? There can be two interpretations: the current dir and the .git dir. -- cgit v1.2.3 From bd59179e090d8443f4fbaa0f4c0ac586fc8dbbb3 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 9 Jun 2010 13:45:18 -0400 Subject: response --- doc/setup/byhand/discussion.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'doc/setup') diff --git a/doc/setup/byhand/discussion.mdwn b/doc/setup/byhand/discussion.mdwn index 97ae40438..941976789 100644 --- a/doc/setup/byhand/discussion.mdwn +++ b/doc/setup/byhand/discussion.mdwn @@ -1 +1,7 @@ What directory is the 'working copy'? There can be two interpretations: the current dir and the .git dir. + +> It is fairly common terminology amoung all version control systems to use +> "working copy" to refer to a checkout from version control, including +> copies of all the versioned files, and whatever VCS-specific cruft that +> entails. So, a working copy is everything you get when you `git clone` +> a repository. --[[Joey]] -- cgit v1.2.3