Thanks!
I ran into issues when just renaming the ebuild. Seems like the python2.7/Python3 handling doesn't work properly any more within portage. For the past few weeks I've been trying to get Python 3 support working as a separate patch (Gentoo-only). Configure and most of the build is now working on a Python 3-only system, but there are a few more scripts that need to be done. After that I want to do a little bit of testing before getting it in, but might be that the next version is released by then. In that case I'll move on to the next version.
Recently, I wrote some more context on my motivation to go this way: https://github.com/BioMike/gentoo-seamonkey-patches/issues/1
Hello, just wanted to ask about the current state. Some sites (which check User Agent strings) already tell me that my SeaMonkey is outdated. However, now we have several libs in portage updated (gpgme, abseil-cpp, poppler, boost, icu,...) which all cause rebuilds of the huge programs like qtwebengine, qtcore, Firefox, LibreOffice, Inkscape, Darktable, also SeaMonkey and whatnot. So it would be a nice opportunity to update SM with that step instead of recompiling the same code. (I still have Python 2.7 along the 3.9 3.10 and 3.11; and as far as I read upstream also wanted to migrate away from Python 2.7?) Not wanting to create pressure, just asking if there might be a foreseeable date, so I know if to delay all these updates for a couple of days or to rather pull them in already.
See https://bugs.gentoo.org/698980#c21.
To add to that. To get 2.53.16 working it would need 20-30-something patches. I'm basically waiting for upstream to get 2.53.17 out (even their beta is delayed), rather than to spend a lot of work to get this version working. So, consider this version to be skipped. I'll keep this bug open until 2.53.17 gets released.
Thanks for the explanation/heads-up. I'll be compiling then and switch to 2.53.17 later.
(update note: Today (August, the 4th) SeaMonkey 2.53.17 was released.)
Great! Took a while, but finally we can make steps forward. I already tested the beta through portage, so I don't expect much difficulties here.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dcb7f431a283a8e392a546198a1f3d8de5e5db68 commit dcb7f431a283a8e392a546198a1f3d8de5e5db68 Author: Myckel Habets <gentoo-bugs@habets-dobben.nl> AuthorDate: 2023-08-06 19:18:14 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-08-07 04:18:31 +0000 www-client/seamonkey: Update to version 2.53.17. - Bumps seamonkey to version 2.53.17. - Fixes implicit function declaration. Closes: https://bugs.gentoo.org/904392 Closes: https://bugs.gentoo.org/905825 Signed-off-by: Myckel Habets <gentoo-bugs@habets-dobben.nl> Closes: https://github.com/gentoo/gentoo/pull/32201 Signed-off-by: Sam James <sam@gentoo.org> www-client/seamonkey/Manifest | 3 + www-client/seamonkey/seamonkey-2.53.17.ebuild | 541 ++++++++++++++++++++++++++ 2 files changed, 544 insertions(+)
Compile was successful, it doesn't crash while playing a youtube video for example, however there is no sound at all - but this is a generic problem with pipewire, at least on KDE; some things work, some don't. Thanks for the new ebuild, Myckel!
