Randy W. Sims wrote:
Ovid wrote:
> Because we still put "require 6" in Build.PL and their "perl Build.PL"
> chokes and they see pretty quickly what's going on (we hope.) Then at
> least there's a chance of them figuring out how to resolve the problem.
> So far, putting stuff in the indexer is the best idea I've heard.
Hmm, this could probably be fixed easily also. Either by using a Apache
handler for directory listings (?not too familiar with web development,
but isn't that what is used when a directory listing is requested?) or
by having PAUSE generate/update an index file for each module/author
directory at the time of submission. If it's a P6 distribution, the
listing could display a special icon. Not sure how this would affect
performance of the server...
Not so much so if the icon is referenced in the CSS file -- that way it's
downloaded and cached, and addressable by simply changing one segment of the
document .. class or ID ..
heck, this way, you could even change the colorscheme of the page easily by
substituting one class or id wrapping the page contents, to signify we're
looking at a Perl6/5 item. :)
Might be a good idea to run this whole scenario by Andreas Koenig, and
then by the folks over on the perl6.language list. There may be valid
reasons for wanting a seperate server, but I can't think of anything
off-hand.
