Hi all, This message is sort of a call for help from anyone who may build and use SeaMonkey. I updated the package the other day, went to use it and noticed that it doesn't behave as I expected.
Specifically, Enigmail is the issue and all this could be my fault. During the SeaMonkey update from 1.1.1 to 1.1.8, I changed some things (not many, mostly just the build patches). Additionally, I used the Thunderbird instructions for installing the enigmail.xpi that is created during the build. Using the T-Bird instructions which runs an instance of SeaMonkey by the root user using the --install-global-extension (or something along those lines, I don't remember), I thought all was good. But Enigmail didn't install. By the time I realized it, I had already removed the SeaMonkey build and source dirs. So I didn't test the make (SomethingOrAnother) install of Enigmail as the book says to (shame on me). Question 1: Does the make (SomethingOrAnother) install of Enigmail work as described in the book to make it globally available for all users? So, I used the alternate method of installation, and it didn't work as well because non-root users cannot do it. You must install the .xpi file as root, run SeaMonkey one time as the root user to register the Enigmail extension, and then all is good. In fact, this makes it globally available. As best as I can tell, there is no way (at least I don't know how) to install the Enigmail extension by non-root user. Question 2: Does this mirror other folk's experience with this? I know Bruce and Alexander build/use SeaMonkey so perhaps they can provide helpful comments. -- Randy rmlscsi: [bogomips 1003.22] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 17:18:00 up 35 days, 8:06, 1 user, load average: 0.02, 0.08, 0.08 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
