[M3devel] multiple pkg roots

[Randy Coleburn]

>From the discussion, it seems to me that we may be mixing two different things.  One is how to deal with evolution of CM3 itself where you may need older variant to build newer variant.  Using Olaf's "pool" terminology, each variant (version) would be in a different pool I suppose.  

The other concept is that of maintaining one or more "public pools" for use by multiple developers--perhaps aligning pools on project boundaries--ie. developers on Project A get access to pools A1, A2, ... while developers on Project B get access to pools B1, B2, ... or some such.  Plus, also having multiple "private pools" for use by individual developers  

Not sure I'm understanding exactly what is being proposed, so I welcome you to set me straight.

Question:  Have you used CM3IDE (the old Reactor) and observed how it allows for one "public pool" and multiple "private pools"?  It also allows each developer's list of "private pools" to be independent.  That is, Developer A's list of "private pools" could be different from Developer B's list.  In CM3IDE the term it uses for "pool" is "package root".  Each developer is free to adjust his/her list of package roots at any time, though changing the public package root would not make sense unless you had multiple CM3 installations from which to choose.

Perhaps my understanding of what is meant by "pool" needs clarification?

Regards,
Randy Coleburn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090706/08a37acf/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4550 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090706/08a37acf/attachment-0002.bin>