I'm getting them from tests where ASDF upgrades itself. These are not constant redefinitions (or not primarily, anyway): primarily they are function and method redefinitions, as a new version of ASDF replaces an old one. In this case, I would like to be able to throw these away, because they clog the output, and they are to be expected.
Feature Request: Add REDEFINITION-WARNING class
I have cloned the repo, and installed boost and boost-build using Homebrew on the Mac. I copied the configuration files as instructed, but I am getting this error with b2 release: ~/src/owlcpp $ b2 release /usr/local/Cellar/boost-build/1.76.0/share/boost-build/src/build/project.jam:259: in find-jamfile from module project error: Unable to load Jamfile. error: Could not find a Jamfile in directory '/usr/local/Cellar/boost/1.76.0'. error: Attempted to find it with pattern '[Bb]uild.jam [Jj]amfile.v2...
The text beside that is "unknown." I changed it to "ultimate," but when I go back...
This has never happened to me before: I was bcc'ed on a signed message I sent out,...
Grrr.... now Sourceforge is jamming Markdown-expanded-to-HTML into commit messages....
I wonder if it would be worthwhile just moving wholesale to github. I really don't...
Summary: Move (incorrect) REQUIRE into garnet-l...