lassik

Concretely, something like this (but better): ``` make OFFICIAL=MacPorts STklos version 1.70 (MacPorts) make # from source tarball without git STklos version 1.70 (unofficial) make # in git repo STklos...

Yes, they are. IMHO even if one downloads a release tarball and builds it, it should still say "unofficial" or "self-built" or something like that. Building software has many complications....

If a bug report says "self-built" that leads naturally to questions such as "did you change any files", "what configure flags did you use", etc.

If the user would have to type `make official` instead of the usual `make` then it is unlikely to happen. (Could use an even less ambiguous word than "official" :-)

From experience, it won't be accurate unless it's unstable by default. `make` should take a string whose default value is `self-built`. MacPorts can pass the string `MacPorts`, etc.

> I'll check the RnRS license status. I am sure this have been sorted out before, because other Schemes have been packaged for Debian, and I think lots of them...

Not sure if there is a more formal license somewhere. The TeX files are collected here: https://github.com/schemedoc/rnrs-metadata There may be other files in the original tar archives that contain those...

We'd best ask @weinholt about that. I'm not well versed in the details of copyright law or Debian policy.

I think the confusion is because that paragraph doesn't have a formal name like "GPL" or "BSD". It doesn't have a SPDX-License-Identifier (though perhaps it could?)

> > If I understand correctly, the core of Unibeautify is essentially a huge data structure that maps programming languages and formatting options to compatible external formatters and their command...