>    # cd /usr/pkgsrc/audio/lame && cvs -z5 update -Pd

Of course, if you would not have thought to do that on your own, Jeff,
then you should be advised: pkgsrc is full of cross dependancies.  I don't
know about lame, but be advised that updating only parts of pkgsrc may
result in wrinkles from time to time.  Most obviously, you may build <x>,
which depends upon a newer version of <y>, so you'll have to manually
update <y>'s pkgsrc before resuming a build.

pkgsrc is designed to eliminate such manual interventions.  But it can
only do this job correctly if it is coherently maintained.  Fragmentary
updates, such as Lubomir suggests, can break this.

Also, if I were doing such a fragmentary pkgsrc update and thought that
I'd found a bug, I'd feel that I should at least get a coherent pkgsrc
(i.e., synchronized) before asking for help.


However, as Lubomir says, there are trade-offs.  I value my own time
rather more than my computer's time (I administer it for myself).  I'd
rather let the computer update a larger-than-necessary fraction of itself
than manually try to determine just which parts I really want to update.
If you're being paid to keep one or more machines humming along with a
minimum of downtime, you may have a different priority, or if it costs you
a significant amount of money to download lots of updated files.


  ``I probably don't know what I'm talking about.'' --rauch@math.rice.edu