The original Planet had explicit rules for versions, and in practice I found they got in the way almost as often as they helped. Worse, when they did get in the way, there was no way around them. I have not looked at Planet 2 in detail yet, but it looks like it has a simpler model where versions are dealt with directly by maintainers and clients. So while Planet 2 isn't doing the work for you, it's also not keeping you from doing what you want/need to do. This isn't ideal -- I'd really like a system that does all the nice things you mention, Tobias -- but only once someone has a design that really gets it "right". Until then, I'd much rather have my options open and a system that stays out of my way. <div class="gmail_extra"> Carl Eastlund <div class="gmail_quote">On Thu, Nov 8, 2012 at 5:22 PM, Tobias Hammer <<a href="mailto:tobias.hammer@dlr.de" target="_blank">tobias.hammer@dlr.de</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Just out of curiosity: What are your / the teams objections against some kind of real versioning system that allows to * specify a version number without creating a new package * specify dependencies based on minimal version * keep/pin a package at some particular version (maybe your code depends on an exact, even buggy behavior) * keep directory and file names between incompatible versions without getting banned from solar What made me also wonder when i read the docs is, why is it allowed to have packets that have the same directories as the core racket distribution? Tobias<div class="im HOEnZb"> On Thu, 08 Nov 2012 14:16:58 +0100, Jay McCarthy <<a href="mailto:jay.mccarthy@gmail.com" target="_blank">jay.mccarthy@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Now that the 5.3.1 release is finished, I've just pushed the beta release of Planet 2 to the Racket core. I've tried to answer all questions and explain everything about Planet 2 in the documentation, which I've uploaded a copy of here: <a href="http://faculty.cs.byu.edu/%7Ejay/tmp/20121108-pkgs/planet2/index.html" target="_blank">http://faculty.cs.byu.edu/~jay/tmp/20121108-pkgs/planet2/index.html</a> In particular, it explains what the plan is to go from this beta release to the final release. If you currently have packages on Planet 1, I am excited to help you make the transition to Planet 2. (I am currently in the process of converting my packages.) Please do not hesitate to let me know how I can help. This represents the third iteration of the design of Planet 2. (The first was worked on from August 10, 2010 to March 11, 2011. The second in July 2011. The third from August 2011 until now, although coding didn't begin until December 2011.) Enjoy, Jay p.s. In the implementation, I'm particularly proud of the little language for defining command-line interfaces with matching functions (see planet2/main.rkt for a use) and the testing infrastructure that allows you to run sequences of shell commands and check their output (see tests/planet2/tests-install.rkt for a nice example.) </blockquote></div><div class="HOEnZb"><div class="h5"> _________________________ Racket Developers list: <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a> </div></div></blockquote></div> </div>