![]() I tried to compile the latest /seamonkey-2.49.5 and it fails at this point: Mozilla on the other hand has given up many years ago, and it shows. Other projects transitioned to cmake or meson/ninja and they, for the most part, work fine. What madness is this? This madness comes from a code base that has not been maintained in many years really. I typically need either python-2, and/or autoconf-2.13. ![]() I can understand people not being extremely eager to go through it: That can be handled in a generic manner by labeling packages as "secure" or "not secure" etc.īuilding seamonkey, as it is with everything else Mozilla dishes out, is hugely annoying though. You are not responsible for their own actions. It's perfectly fine to tell people that there are security issues (and this is the case for other projects too, by the way, so I don't see why this arbitrary distinction should exist). I just disagree that it should be up to others to dictate use cases onto others when it comes to any general purpose linux distribution. ![]() If someone wants to use seamonkey, why should you or anyone else forbid this? It's fine if you can not do so or do not want to do so lack of time is a completely valid reasons. IMO that should not be up to you, or anyone else to decide, for OTHERS whether their use case includes wanting to use seamonkey or not. I agree in the sense that mozilla has lost it completely some years ago, so I would be sceptical of their code (actually including FF, so I am not sure why FF should be treated differently to seamonkey here I'd be wary of anything mozilla touches these days).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |