![]() ![]() If you want to use it, you have to ensure that you have the legal right to do so and that you do not infringe any trademark rights. ![]() This work includes material that may be protected as a trademark in some jurisdictions. See version 2 and version 3 of the GNU General Public License for more details. ![]() This work is distributed in the hope that it will be useful, but without any warranty without even the implied warranty of merchantability or fitness for a particular purpose. This work is free software you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation either version 2 of the License, or any later version. LGPL GNU Lesser General Public License true true See version 2.1 and version 3 of the GNU Lesser General Public License for more details. This library is distributed in the hope that it will be useful, but without any warranty without even the implied warranty of merchantability or fitness for a particular purpose. This library is free software you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation either version 2.1 of the License, or (at your option) any later version. Mozilla Public License Version 1.1 MPL 1.1 true See the License for the specific language governing rights and limitations. Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. The contents of this file are subject to the Mozilla Public License Version 1.1 (the "License") you may not use this file except in compliance with the License. It is recommended to name the SVG file "Seamonkey Suite Logo.svg" â then the template Vector version available (or Vva) does not need the new image name parameter. If an SVG form of this image is available, please upload it and afterwards replace this template with. This has several advantages see Commons:Media for cleanup for more information. Searching through the code, I've encounter various spots that call python2.x, which might give issues that surface downstream the build process.This logo image could be re-created using vector graphics as an SVG file. So, to completely go Python 3, that has to be tackled as well. Seamonkey seems to be the only user of that enigmail version as well. I'll have to dive into this deeper.Īnother dependency (through the "crypt" USE flag) that requires python2 is ![]() It was pip that caused the exception btw. I got an exception where it tried to setup third party supplied setuptools, pip and wheel to setup a "virtual environment". I did a quick check this morning by removing the Python 2 support code from the eclass and see if Seamonkey would build. I think it is better to remove python2 usage althogether, than to add a variable for something that is clearly EoL. I think fixing the python2 issue should have the main focus for now, rest can come later. > variable that seamonkey can set to allow Python 2 usage. > If the rest of the logic is the same, it'd make more sense to just have a But:Ä¡: I kind of hope the main mozilla maintainers returns who opposed to that idea,Ä¢: it doesn't bother _that_ much having them in the ebuilds andÄ£: I guess history did show that we need to modify the eclass too often.Īlso I imagine the eclass-way breaks overlays and whatever downstreams are relying on us packaging it. Well, _I_ would prefer to move the functions from ebuilds to an eclass. > determine if it suits to re-add to the other packages. > for Seamonkey (with keeping FF/SpM in mind) and than we can at a later point > currently the only one actively using it, I'll try to make it better suited > it gives me enough motivation to have look into this. > As for FF/SpM reusing them, even if they don't want to do this at this point I'd imagine the PYTHON_COMPAT declared in seamonkey, andÄ«DEPEND="$" in the ebuild is enough to declare the required python interpreter to build seamonkey. Since seamonkey is the only one using -v6, if you are sure it doesn't require python-2.7 to build, we can just drop the BDEPEND from that eclass. I quite honestly don't see the point of adding new eclass just to "drop" python-2.7 support. > but let Seamonkey (and later Firefox and newer Spidermonkeys) use the newer > python2.7 support? We can than keep the old ones for the old Spidermonkey, > possible to add a new one with a bumped version (v7) that does not contain > Seeing that there are two versions of these eclasses in tree, would it be (In reply to Myckel Habets from comment #5) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |