I discussed with andre and we would like to collect some rules. In fact we would like also to extract the rules from the history of configuration :) - Baseline should have a blessing base line - Version should have a development I imagine a lot more of them/ If you had ideas just send them. Stef On Oct 1, 2012, at 11:54 PM, Dale Henrichs wrote:
Not sure whether or not these are doable with Slime, but they are good ideas
Dale
----- Original Message ----- | From: "Alexandre Bergel" <alexandre.bergel@me.com> | To: Pharo-project@lists.gforge.inria.fr | Sent: Monday, October 1, 2012 1:30:44 PM | Subject: Re: [Pharo-project] Metacello bleedingEdge question | | > I was thinking in terms of Slime for Seaside. | > One PhD student is working on rule and I was thinking that it would | > be fun to have a kind of | > Metacello checker. | > do you have some rule of thumb where to look for potential | > problems? | > Because it can be a fun experience. | | I had this idea of a checker for Metacello (that can be used with | Versionner before committing), but never got the traction to do it. | Some rules: | - two packages in a graph of dependencies may rely on a different | version of a third package | - identifying cycles in packages | - very important: checking whether the dependencies defined in | Metacello matches with the actual source code. Said in other | words, do I miss some dependencies in a configuration? | | Cheers, | Alexandre | | -- | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | Alexandre Bergel http://www.bergel.eu | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | | | | |