Howdy, is it save to assume that the --distro-compatibility option of our configure script has no popularity at all and can be removed again? I introduced it upon request more than two years ago to provide third-party distro makers with a build time switch to disable Haiku trademarks (respectivly enable the correct ones). The build system defines a build system variable and a preprocessor macro, neither of which are used in any Jamfile or source code (unless I missed something) despite having been readily for so long. Since the first release is almost upon us, we should either implement the feature or drop it altogether. CU, Ingo PS: The default "distro compatibility" level, which probably everyone is using, means "not Haiku compatible", which, at least theoretically, disables all Haiku trademarks. In practice, since it failed to be adopted, the configure switch doesn't have any effect.