pseudo-install.pl assumes MANIFEST is in PLUGIN/lib/PLUGIN directory.
BuildContrib can find it in PLUGIN/lib/PLUGIN, PLUGIN/lib or PLUGIN.
Confirming this, but is this an issue? I suppose if the MANIFEST is in multiple locations,
BuildContrib will find/use the first one in the path, while pseudo-install only uses the one in the lower directory.
Is fix - change
BuildContrib to only look in the lower directory, or change pseudo-install to search the path? If the two install paths end up using different MANIFEST files without warning, I suspect that this is a bug, not necessarily an Enhancement.
--
GeorgeClark - 16 Mar 2011
The extra search path in buildcontrib is only there because of the special case of the core - which is never pseudo-installed. Not a bug, though there is a bad report if a manifest can't be found which I have fixed.
--
CrawfordCurrie - 07 Mar 2013