Re: [Pharo-project] [MC] Adding a constraint when declaring a required package

Stéphane Ducasse wrote:

Keith

the problems with such approaches is that each of these nice little extensions will break the analysis tools we are developing. I would prefer a good and stable solution over everybody can hack its own. I want some invariants on top of which we can build other tools.

Stef That is entirely the point. When people roll their own, you end up with endless variations. (i.e. no stable situation)

This at least attempts to capture and codify the use-cases that people have. Since PackageInfo is in charge of what is and is not in a package then your "tools" have to query package info anyway. Keith