How about someone simply (better than I) updating the manual page and
pkg_info output with warnings and clarifications about the intended use
case and risks?

Maybe the man page could say (just as an idea): "Warning: this is intended
to suggest files for removal, that it guesses are obsolete; if you build
software locally or modify other system files, it may mistakenly suggest
removal of libraries or other files that you want to keep.  It should only
be used by those who are familiar with their system and accept the risks
involved [and maybe?:  or who know for certain they have not changed
anything ... in the directories it checks.]" Followed possibly by something
like:  "It has not (yet) applied the lessons of "find -print0" and "xargs
-0", and could recommend removing something you don't expect: review
carefully its output before proceeding with file deletions."

And in the man page and pkg_info output, wherever "obsolete" is found,
something like: 
< [...] It only reports obsolete
> [...] It only reports *possibly* obsolete [...]; see the manual page for
> more information.

And similarly in the upgrade guide, if it were mentioned there in the future.

Another possible step could be making it emit a concise message about the
risk and intent, when it runs, if there is a practical way in a
comment near the beginning of the output without breaking its function;
or comment the output with that included so users have to think before
they can use it (passing a switch or something).

With some of those, maybe it can remain in the learnable flow, for new or 
maturing users.

Just thoughts; if not helpful, forgive the noise.

Reply via email to