pkg lock

@lbutlr kremels at kreme.com
Mon Sep 9 15:20:59 UTC 2019


Before I go off on a wild tear, a couple of quick questions.

If I want to prevent pkg update from overwriting a package I built from ports, I need to issue a pkg lock <port> first, then if I want to rebuild it with postmaster I pkg unlock <port>, rebuild/update the port, and then lock the port again, yes?

And there is no one-step way to say via flags or something, unlock, rebuild, then lock at once?

Also, is there anyway to tell what has been installed via ports and what has been installed via pkg? Or better, what has been installed with custom options that differ from the pkg versions?


-- 
WHO KNOWS WHAT EVIL LURKS IN THE HEART OF MEN?  The Death of Rats looked
up from the feast of potato. SQUEAK, he said. Death waved a hand
dismissively. WELL, YES, OBVIOUSLY *ME*, he said. I JUST WONDERED IF
THERE WAS ANYONE ELSE. --The Truth



More information about the freebsd-questions mailing list