> You can try sudo port upgrade outdated and not <portname> Thanks, I have forgotten the syntax for that. I guess I could make an alias/function of it.
> An even better feature would be a custom marking procedure that would allow a > user to “label” certain ports That would be ideal. Would it be feasible using a git checkout to manage all ports? On 14 Feb 2017, at 17:52, Carlo Tambuatco <[email protected]> wrote: > An even better feature would be a custom marking procedure that would allow a > user to “label” certain ports such as mysetofvideoports or mysetoftexteditors > or whatever and then allow port actions to ignore or perform > operations on just those sets. You could then create your own custom > blacklist or whitelist or whatever. > > The only label that I know of right now is setrequested and unsetrequested. > > >> On Feb 14, 2017, at 10:12 AM, Richard L. Hamilton <[email protected]> wrote: >> >> Sure would be handy if one could optionally have ports that failed to >> upgrade blacklisted (for that version only), so that “port upgrade” could >> still do everything else. >> >>> On Feb 14, 2017, at 8:15 AM, Carlo Tambuatco <[email protected]> wrote: >>> >>> You can try sudo port upgrade outdated and not <portname> >>> >>> or >>> >>> sudo port upgrade outdated and not <portname> and not rdependentof: >>> <portname> (not sure of the exact syntax, here) >>> >>> To ignore a port and its recursive dependencies… >>> >>> >>> >>>> On Feb 14, 2017, at 6:03 AM, db <[email protected]> wrote: >>>> >>>> How can I mark a port to not be upgraded by `port upgrade outdated`, for >>>> example, one that has a bug in my system version? >>> >> >
