On Thu, 16 Aug 2007, Alec Warner wrote: > On 8/15/07, Vaeth <[EMAIL PROTECTED]> wrote: > > > > In all of the above cases you usually want that the corresponding > > packages are contained in the next emerge -NDu world; you just want > > to exclude the packages for one particular call of emerge. > > Ahh but that is a lie. > You want to exclude the package from the depgraph until whatever > reason you had is gone. > Typically it's 1 emerge run, sometimes it's 100's, I don't think you > can necessarily limit the number of emerge runs in any of the use > cases.
This is true. But as you say: Typically it is only one run, i.e. *typically* the feature will help you. > Your latter example about not > removing the mask is mitigated by using a tool (mask, run emerge, > unmask). Unfortunately, such a tool always has side effects. Just imagine the situation that you started an update (with something temporarily excluded) and then realize that your net access will soon go down [which is not unusual on a laptop] and therefore you want to download everything with emerge -f... Anyway, meanwhile the situation has become much better by allowing directories for /etc/portage/package.*: One can add the temporary hacks into a special file like /etc/portage/package.mask/onlynow and then remove this file without modifying the "more permanent" stuff. Unfortunately, this approach is not possible for /etc/portage/profiles/package.provided which might be sometimes needed if masking is not possible (e.g. if something else depends on the masked version). -- [EMAIL PROTECTED] mailing list
