On Tue, Nov 30, 2010 at 6:03 PM, Michael K. Johnson <johns...@rpath.com> wrote: > On Tue, Nov 30, 2010 at 04:13:59AM +0100, Martin Baehr wrote: >> On Mon, Nov 22, 2010 at 07:50:51PM -0500, Michael K. Johnson wrote: >> > 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. > > Well, the "installed set" is jargon; we have to call that set > something. The "installed set" are the packages that would be > installed if the model ended there. Calling them the "would be > installed if the model ended here set" would be verbose... :) > > But I'll re-read the man page and see if I can make that easier > to follow. >
Newer versions of Portage uses "@selected" which translates to the 'selected set'. The idea in Portage is that @world - @system = @selected. However, I'm not sure how well the Portage sets @system, @world and @selected translate to Conary's notion of things. In a system-model context, however, I do think it makes sense to refer to the stuff that we are about to install as the 'selected set' -- i.e. the packages that would be installed/removed by changing the system-model and running conary sync. In other words: 'installed set' + 'selected set' = 'new installed set' after conary sync has completed successfully. Hope that made sense. -ermo _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
