This has nothing to do with MC, but with how PackageInfo defines what belongs in a package. 5 years ago one could override PackageInfo in a package to define different rules, so you could have easy defined a different split. Unfortunately this is no longer possible due to hardcoded PackageInfo semantics everywhere. The only solution is to stick with consistent and well though package name scheme. Not the only possible naming strategy, but the one we developed for Seaside works pretty well: http://code.google.com/p/seaside/wiki/PackageNaming Lukas On 12 August 2011 22:14, Damien Pollet <damien.pollet@gmail.com> wrote:
Is there a clear doc somewhere about how to deal with MC packages that have a common prefix ?
e.g. I currently have Coral
I want a separate Coral-Examples, and from how MC behaves I have the feeling it's not possible⦠When do we switch to git already ?
-- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet
-- Lukas Renggli www.lukas-renggli.ch