From: Bodo S. <bo...@le...> - 2009-01-29 18:00:49
|
As there seems to be no standard and no simple solution to this problem, how about going the dead simple way of installing .../src/ modules in .../lib/external/ instead of .../lib/ Then, when making the dist, simply skip external/ Bodo > Michael Peters wrote: > > Noam Weinstein wrote: > > > Hmm - That's a tricky one too! I don't know the answer about CPAN, but if > > > > there's no way to do that programatically, > > > > We could possibly look at the svn:ignore property of lib/ and include every > th > > ing not matched by that? > > Downside: You'd have to maintain svn:ignore and you'd have to remember > that this property list has a hidden feature. Frankly, I don't like this > kind of silent hijacking of things meant for other purposes. I will bite > you in the end. > > > > perhaps a decent workaround would > > > be to add an optional directive called something like AddonLibs to > > > krang_addon.conf that lists only the libraries specific to the addon, and > > > > then when krang_addon_dist runs it could ignore paths beneath [addon]/lib > > > > that are not in the list? > > > > This is usually done with a MANIFEST (and optionally a MANIFEST.SKIP) file > in > > most software projects > > (Perl and non-Perl) that I've come across. So if we decide we need it we sh > ou > > ld probably stick with > > something semi-standard. > > Hm, the MANIFEST lists the files coming with the module distribution, > but they don't list the files that will finally be installed. > > Best, > > Bodo |