Reputation: 5041
I try to learn about RPackageTag
s:
RPackageTag
s are just something like sub-packages?RPackage
? The tags in Package1-Tag1 and Package2-Tag1 are not the same, i.e. are two different instances of RPackageTag
?RPackage
and also the possibility that Package1-Tag1 is the combination of RPackage
Package1 and RPackageTag
Tag1?Is that right? What is the idea behind the introduction of RPackageTag
s?
How are RPackageTag
s related to Monticello packages?
Upvotes: 1
Views: 53
Reputation: 4357
Some answers:
Of course, as you can see, the real problem here is to have an ancient way of organisation still in system. This will change, in Pharo4 or (most probably) in Pharo5, and for now we need to live with this convenience solution.
Upvotes: 2
Reputation: 13386
Ring package structure was adopted in Pharo 3. Approximately what was known to be an MC package became RPachage, pure-smalltalk categories disappeared and were replaced by RPackageTag
s. You can think about it as a way to create categorise classes inside your MC package. I don't know what Pharo board will decide in future, but for now you can have only 1 tag per class.
Upvotes: 0