On Mon, Nov 22, 2010 at 07:50:51PM -0500, Michael K. Johnson wrote: > > RTFM > I tried in 2.2.0 beta to improve the man page descriptions of system > model update operations. Let me know if it's still confusing;
not as far as i can tell now. the only nitpick i have is that the description of the system-model file talks about the set of to-be-installed troves as "installed set". but "installed set" makes me think of the troves that are already installed. maybe a grammar issue, or a limitation in my english understanding. "To make Conary not update a version when you use the conary updateall command, double the appropriate = in the system-model file." sounds complicated andeasy to missunderstand, also, what if there is no version in the file? maybe instead: "use == and the version" this brings me back to the discussion about the difference to conary pin. i still think that they should be the same and pinned troves should be added to the system-model. if only to simplify things for the user. i believe that for simplicity and consistency of the interface normal operations on the system-model should be doable through conary commands. the handling of versions and == should also be explained a bit further down where the individual commands for the system-model are explained. what is the difference between troveSpec and troveSpec+? greetings, martin. -- cooperative communication with sTeam - caudium, pike, roxen and unix services: debugging, programming, training, linux sysadmin, web development -- pike programmer working in china community.gotpike.org foresight developer (open-steam|caudium).org foresightlinux.org unix sysadmin iaeste.at realss.com Martin Bähr http://www.iaeste.at/~mbaehr/ is.schon.org _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
