Hi all,
I've just dropped lash to the AUR. It has essentially been dead for nine
years, which is why I don't want to spend any time fixing it, or
including it into any softare in the main repositories.
AFAIK, all projects depending on it, can be built without it and
non-session-manager is a more modern approach (as the application only
needs to implement an OSC interface) anyways.
If this is not the case and your AUR package depends on lash, you will
have to fix lash and its issues with current glibc (removed Sun RPC), as
it introduces a new dependency on libtirpc.
Best,
David
--
https://sleepmap.de
i suspect this concern is a bit belated - it probably goes back to the release
of JUCE v5 in april 2017 - i dont think anything has changed since then - quite
a fuss was made at the time like starting the very next day
the GPL is still an option but it was removed from mention on the website and
now is essentially a secret - new users need to actually download and read the
source code or download and run the binary to learn that the GPL was an option
i could point you to this discussion that tried to address the down-playing of
the GPL option and the possibility of a community fork to remove the anti-
features
https://forum.juce.com/t/should-the-community-consider-a-juce-fork/22056