On Fri, Mar 10, 2006 at 03:18:25AM -0500, Joey Hess wrote:
> Matt Kraai wrote:
> > > BEGIN {
> > > $blosxom::version="is a proper perl module too much to ask?";
> > > do "/usr/bin/markdown";
> > > }
> > >
> > > Markdown::Markdown($text);
> >
> > [I don't know much Perl, so I hope you'll bear with me.]
> >
> > You're suggesting that I create a module under /usr/lib/perl somewhere
> > with the above code? What should I call it? Where should it go?
> > What else should I ask?
>
> Sticking that in a perl module would actually work, and is probably the
> minimal patch to fix this bug, but it's ugly beyond belief. Note the
> disgusting use of $blosxom::version to trick markdown into thinking it's
> being run by blosxom, and so behave sorta as a library -- but avoid
> actually running any of the blosxom-specific code. Highly implementation
> dependent, could break anytime. Which is why I don't like having that
> code in my wiki right now..
>
> I've attached a patch that does it a bit more cleanly while still being
> minimal enough to maintain if upstream doesn't accept it.Thanks for the patch. > (BTW, your rules file sucks and leaves debian/files behind after > debian/rules clean.) Thanks for notifying me of this. I've made it remove debian/files. The rest of it still sucks, though. -- Matt
signature.asc
Description: Digital signature
