Using smart

[Mikus Grinbergs]

On Wed, 12 Apr 2006 10:41:58 -0300 Gustavo Niemeyer <gustavo at niemeyer.net> wrote:
> > The RMB-on-package GUI for 'Priority' only lets me specify
> > preference by channel, NOT by package level.  And the generic
> > "Edit Priorities" window *forces* me to TYPE in lots of info
> > (rather than letting me select info by clicking).
>
> Try right-clicking on the package you want and selecting
> "priority".

My first sentence (that you quoted) says that doing so lets me
specify priority per channel.  What I am concerned about is that
while I would want 'smart' to NOT upgrade to the package available
today from a particular channel (because THIS package specifies
out-of-date dependencies) -- I however want 'smart' to accept
tomorrow's (anticipated) package from that same channel (which
has hopefully been fixed to specify up-to-date dependencies).

If I were to blindly put in -10 as the priority, wouldn't that be
applied to all same-name packages that came from that channel ?

>
> > HOW ought I specify to 'smart --gui' (so I can use
> > 'Upgrade all packages') that there is a SPECIFIC LEVEL
> > of a newer package that I DON'T want to upgrade to ?
>
> I'm not used to the term "package level". Can you please
> explain what it means?

I am not familiar with exactly how to refer to the naming
conventions used with packages.  I was trying to express that
I want (tomorrow's hypothetical) package 'ImageMagick 6.2.3-4.2.1'
to be unaffected by whatever I specify for (today's real) package
'ImageMagick 6.2.3-4.2'. I made up the term "package level" to
differentiate between such two instances of the package identified
as: 'ImageMagick 6.2.3'.

mikus