Closed olbat closed 5 years ago
I reported this on the compiler some time ago: https://github.com/crystal-lang/crystal/issues/7602 Not sure how to fix that though
You're right, I think this is the same issue. Seems that I missed it :-s Apparently it was affecting Crystal 0.27.2 as well...
Not sure how to fix that though
Same thing for me, I don't really know what would be the best way to fix it.
Packaging can be fixed, however I find the way it's done ATM is a bit weird. I mean having some piece of code in the source making a relative reference to something outside of the source path.
Having the VERSION file in the src/ directory does not seems OK either and having a version.cr class/module has a lot of drawbacks...
The VERSION file that is used by compiler/crystal/config.cr is missing from both Debian and Archlinux packaging.
This leads to errors when using the
Crystal::Config
package.To reproduce (full log):
There is no more issue when creating the missing VERSION file on the two distributions. However, for Archlinux, this file is located at /usr/lib/VERSION which might be problematic :-)
I'm not really sure if this is a packaging or code issue. Please just let me know if I should open an issue in the core's repo.
More info about the packages:
Debian
Archlinux
(I only tested with Crystal 0.28.0 on Debian Buster and an up to date Archlinux)