I decided not to use blosxom at all, and I haven't used Perl since
version 4, but it seems like it wouldn't be a ton of work to do both:
support Getopt::Long and look at $ENV. Then, nothing breaks for
anybody.
Gerfried Fuchs <[EMAIL PROTECTED]> writes:
> Hi!
>
> I've today discussed the problem with an upstream developer. Where
> Nick's suggestion to use Getopt::Long for enabling the -f switch we were
> thinking about addressing the problem in a different way:
>
> Getting rid of the -f switch at all and instead use
> $ENV{BLOSXOM_CONFIG_FILE}. This has the added benefit that hosting
> providers might allow their customers to use SetEnv in vhost/.htaccess
> configuration parts for having their own config files.
>
> It would break backward compatibility, so it would require some special
> notice for people who might use the switch currently - though I'm not
> too sure how common it's really used as it is a patch only we ship and
> which isn't available in upstream. Also I rather think people might
> have changed rather the config plugin than using this.
>
> If I don't receive any serious feedback within the next few days I'll
> upload a package that changes in that respect soonish.
>
> So long,
> Rhonda
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
