Release Tag
CryptoCopter opened this issue · comments
Hello,
I'm looking to package mgen for ArchLinux (GCC 11.1.0).
Unfortunately, the current mgen release (V5.1.1
) does not build with the most current protolig release (3.0b1
), but it dows build with the current HEAD
from your repo.
Since it isn't particularly nice to build a package based on a git commit, do you think it would be possible to tag a new protolib release?
Thanks!
MGEN 5.1.1 includes a specific compatible protolib revision via git submodule. Since it was not done previously, I have added new source .tar.gz and .zip files to the MGEN 5.1.1 release that contain the referenced protolib code. I'm not sure if that is helpful to your goals or not, though.
I would agree that it would be a good idea to create a new Protolib release, as the current 3.0b1 release is from 2017.
Than you very much!
That actually solves my issue perfectly