I've seen this in other managers as "pin".
Anyway, this gets tricky with managing dependencies. As you say, this
would probably need to copy the current portfile, but it would also
need to pin and copy anything that depends or is dependent on this
port. And that's going to extend recursively out from there. Plus, if
the upgrade failure is only identified when trying to upgrade, it's
too late to copy the current portfile and the portfile history isn't
maintained locally.
I agree this would be a nice feature, but it's potentially a very
large problem to tackle.

On Tue, Mar 6, 2018 at 9:50 AM, Ken Cunningham
<ken.cunningham.web...@gmail.com> wrote:
> It is fairly common for users to find an update to a port that won't build on 
> their system for some reason.
> It would be nice to have a simple command, like
> port peg PORTNAME
> that stops the port from attempting to update until the peg is released. Such 
> a command does exist in other package mgmt systems.
> This can be done manually with a local repo, but it is a bit of a PITA to do 
> that for casual users.
> Perhaps MacPorts could have a built-in local repo, and "port peg PORTNAME" 
> would copy the current portfile out of the installed registry in there. That 
> sounds pretty easy to do.
> Perhaps there is some easy way to keep a list of ports that are ignored for 
> port upgrade outdated.
> Best,
> Ken

arno  s  hautala    /-|   a...@alum.wpi.edu

pgp b2c9d448

Reply via email to