Re: Dropping enigmail support from enigmail
Thanks for the pointer to enigmail in UPDATING, so I misunderstood the log message and should have looked in UPDATING. However, lightning seems to be gone - I don't find it installed with the port and it does not seem to be offered as an add-on for this platform. On 12/17/16 23:09, Jan Beich wrote: > Martin Birgmeier <la5lb...@aon.at> writes: > >> After upgrading to thunderbird-45.5.1_6 I noticed that enigmail (and >> lightning) support were gone from thunderbird. I tried to find a >> replacement package until I read the svn log message: > Lightning had 2 copies, only one of those was removed. For Enigmail see > /usr/ports/UPDATING from 20161216. > >> I think a decision to remove such an essential component should not be >> taken so lightly, especially when the actual port version (45.5.1) has >> not even changed. > Why the version should change? Enigmail isn't part of Thunderbird distribution > but just one of third-party extensions you can find on addons.mozilla.org. > For historic reasons it was bundled with the port but the requirment is gone. > > ENIGMAIL option was unmaintained beyond updates which were irregular. > And it was bound to get in the way if anyone attempted to refactor the > current maintenance nightmare gecko@ is in. > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Dropping enigmail support from enigmail
After upgrading to thunderbird-45.5.1_6 I noticed that enigmail (and lightning) support were gone from thunderbird. I tried to find a replacement package until I read the svn log message: gecko: drop ENIGMAIL, LIGHTNING to simplify updates ENIGMAIL can still return as www/xpi-enigmail but, alas, xpi-* ports and their framework are mostly unmaintained. So this means that after a simple PORTREVISION change I cannot send, receive, or reread encrypted mails any more. I think a decision to remove such an essential component should not be taken so lightly, especially when the actual port version (45.5.1) has not even changed. What is being planned to remedy this unfortunate situation? -- Martin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
