Mejores prácticas para tratar con archivos no elaborados en una instalación nueva de homebrew

Accidentalmente borré /usr/local/binel que contenía brewentre otras cosas. Reinstalé homebrew y corrí brew prunepara deshacerme de los enlaces simbólicos rotos, pero cuando ejecuto brew doctor, sigo recibiendo la siguiente advertencia:

$ brew doctor
Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
    /usr/local/lib/libtcl8.6.dylib
    /usr/local/lib/libtk8.6.dylib
Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
    /usr/local/include/fakemysql.h
    /usr/local/include/fakepq.h
    /usr/local/include/fakesql.h
    ...
Warning: Unbrewed .pc files were found in /usr/local/lib/pkgconfig.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .pc files:
    /usr/local/lib/pkgconfig/tcl.pc
    /usr/local/lib/pkgconfig/tk.pc
Warning: Unbrewed static libraries were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected static libraries:
    /usr/local/lib/libtclstub8.6.a
    /usr/local/lib/libtkstub8.6.a
Warning: You have uncommitted modifications to Homebrew
If this a surprise to you, then you should stash these modifications.
Stashing returns Homebrew to a pristine state but can be undone
should you later need to do so for some reason.
    cd /usr/local/Library && git stash && git clean -d -f

Si desea ver la lista completa, consulte aquí: http://pastie.org/9663902

Mi pregunta es, ¿debo eliminar manualmente estos archivos? De acuerdo con esta respuesta , simplemente puedo dejar los archivos (o moverlos a una carpeta separada y luego ejecutarlos, brew link <folder name>pero dado que esa respuesta tiene tres años (y sobre binarios específicamente), estoy comprobando si hay una táctica más correcta.