[MacPorts] #66538: Allow suppressing 'Warning: couldn't find file'

[MacPorts]

#66538: Allow suppressing 'Warning: couldn't find file'
--------------------------+--------------------
  Reporter:  esbugz       |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  base         |    Version:  2.8.0
Resolution:               |   Keywords:
      Port:               |
--------------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:2 esbugz]:
 > Actually, it seems it is possible, this flag stops the spam when I
 install new ports, so will add if to the list of default args meanwhile.
 >
 > {{{
 > --no-rev-upgrade
 > By default, a binary sanity check called rev-upgrade is run
 automatically after each successful installation. Pass this flag, if you
 want to avoid running this step, for example if you want to run it
 explicitly later after a number of installations using sudo port rev-
 upgrade, or if you know it will detect problems but want to defer dealing
 with them
 > }}}

 Sure, you can use that flag to prevent the rev-upgrade step from running
 at all. But there is no way at present to have the rev-upgrade step run
 and check for problems with installed files while silently ignoring files
 that you have unexpectedly deleted.

 > By the way, what is `pkg_post_unarchive_deletions` for? Any chance of
 adjusting this to remove the mistaken files (would also help in removing
 the useless locales and some other stuff if possible)? (example below
 didn't change anything). The `unarchive` stage isn't mentioned in the
 Guide, so not sure what exactly it's used for
 > {{{
 > # Space-delimited list of files and directories to delete after the
 unarchive stage and before creating a pkg. Paths are interpreted relative
 to prefix, and there is no default value. This is useful for removing
 unnecessary files and directories prior to pkg or mpkg deployment
 > pkg_post_unarchive_deletions  share/locale share/helix
 >
 > }}}

 I suspect this has nothing to do with the rest of this ticket. If you have
 questions about how the internals of MacPorts work the macports-dev
 mailing list would be a better place to ask.

-- 
Ticket URL: <https://trac.macports.org/ticket/66538#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS