Opened 2 years ago

Last modified 22 months ago

#66538 new enhancement

Allow suppressing 'Warning: couldn't find file'

Reported by: esbugz Owned by:
Priority: Normal Milestone:
Component: base Version: 2.8.0
Keywords: Cc:
Port:

Description (last modified by ryandesign (Ryan Carsten Schmidt))

I've deleted some mistakenly installed port files #66525 and now during the Scanning binaries for linking errors installation step I get warnings for missing files. Is it possible to either limit the scanning step to the port being installed, not to all ports, or at least allow to suppress the warnings and leave them only for port diagnose command?

Change History (4)

comment:1 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)

Neither of those is currently possible. You are expected not to delete any files that ports install.

comment:2 Changed 2 years ago by 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

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

comment:3 in reply to:  2 ; Changed 22 months ago by ryandesign (Ryan Carsten Schmidt)

Replying to 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.

comment:4 in reply to:  3 Changed 22 months ago by esbugz

Replying to ryandesign:

while silently ignoring files that you have unexpectedly deleted.

I could manage its expectations if it allowed some kind of ignorelist

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.

If it does allow me to blacklist some files from landing on my system (and thus not be checked by the scanner), then it's relevant to this ticket

Note: See TracTickets for help on using tickets.