<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Jacob Matthews schreef: <blockquote cite="mid44B2B672.3020105@cs.uchicago.edu" type="cite">I'm not sure I understand the feature you're proposing. One thing I definitely _don't_ want is for PLaneT to ever change which package resolves a particular PLaneT require (in a particular file) without you explicitly telling it to do so --- if PLaneT upgrades your packages completely automatically and something goes wrong, it would be very difficult to figure out why your program worked yesterday but doesn't work today. (If you _want_ to change package's links, then you can use the PLaneT command-line tool or the utility functions provided by the planet collection to do that.) </blockquote> How? And how would I make it link to the latest available package? <blockquote cite="mid44B2B672.3020105@cs.uchicago.edu" type="cite">Are you suggesting that a background thread check for minor revisions to installed packages, and when they become available offer to install them and relink packages that point to them (like, e.g., Windows Update)? </blockquote> Yes, I want to be able to require planet packages, in a way (so I'm explicitly telling that it is what I want), to upgrade minor revisions automatically. Or another way of invoking an update cycle. <blockquote cite="mid44B2B672.3020105@cs.uchicago.edu" type="cite"> That's the rule, but there's no way for us to be sure that package authors follow it (they might even break it accidentally, e.g. by introducing new bugs). The fact that supposedly backwards-compatible upgrades might break things is a very important consideration, so we want to be very careful about features that upgrade things. </blockquote> True. It's a risk and needs quality assurance measures from the developer point of view. Thanks in advance for any comments --Hans </body> </html>