Richard writes:
hi justin,
i've been 'sicked' :-) on you from #irc:
"I'm not sure why the loadplugin line got shoved into active, but
that's jm's thing."
i'm bldg sa-svn r433640 on osx.
on , i now notice, e.g.:
[4087] dbg: plugin: registered
(0x1fcf1dc)
[4087] dbg: plugin: fixed relative path: /var
/
[4087] dbg: plugin: loading
from /var
/
[4087] warn: plugin: failed to parse plugin /var
/ Can't locate /var
/ in @INC (@INC contains: lib
/usr/local / /usr/local
/perl_libs/sitelib /usr/local
/ /usr/local
/perl_libs/privlib /usr/local
/ /usr/local
/perl_libs/vendorlib) at /usr/local
/ line 97.
which is, apparently, coming from the associated lines in Dist/72_active.cf:
grep felicity 72_active.cf
##{
loadplugin
sandbox-felicity.pm
##}
ifplugin
ifplugin
ifplugin
ifplugin
from what i've been told:
"70_sandbox is for stuff that hasn't been autopromoted yet, and
72_active is anything that's been promoted."
i understand that if a loadplugin, etc is "in" sandbox.cf, that one
shouldn't expect it to make sense & follow *.pre rules -- necessarily.
but if it's in an 'official' distro .cf, i'd think the "it" should
behave and follow *.pre rules -- i.e., don't auto-enable plugins without
specific permission.
and, of course, in my example, i have NT enabled the plugin in init.pre.
so, why is a reference to "sandbox-felicity.pm" in Dist/72_active.cf ?
bug? feature? my fubar?
it's because "sandbox-felicity.pm" is listed in MANIFEST, ie. is
considered part of the main distribution. This used to be required
to work around a bug, but isn't any more.
try now I've taken them out.