On 05/01/2012 10:21 AM, Andrew Benton wrote: > On Tue, 01 May 2012 16:00:50 +0100 > "Armin K."<[email protected]> wrote: > >> On 05/01/2012 04:45 PM, Andrew Benton wrote: >>> So does that mean you want it left in the book? >>> >>> Andy >> If you think it's worth keeping and updating, yes. > I don't think it's worth keeping and updating. > >> As I said, I link >> firefox against xulrunner, so Firefox uses it, plus Totem*, Rhythmbox, >> libproxy* and gecko-mediaplayer >> >> In BLFS, Firefox is built as standalone browser, so there are only 2 >> packages left. > I see Xulrunner listed as an optional dep of Icedtea6, Libproxy and > Totem. I'd be happy to see those as external links pointing at > https://developer.mozilla.org/en/XULRunner > >> *Packages in the book - Xulrunner is optional there. Imho, libproxy can >> be removed if necesary since it's only optional by glib-networking. > Libproxy is an optional dep for Vlc, Neon and Glib-networking > >> But there is still java (openjdk). Let's see what's dj going to say >> about this. If he's for, drop it. > Fair enough. Ken, Bruce and Ragnar too.
It really makes no difference to me. Previously, I'd have thought it inaccurate to require FF where XUL was what was actually required. Not so much any more. It made sense when FF, TB, and SB could all use the same XUL build, but this has not been the case for quite some time. It's been a long time since I looked at it, but I think FF and TB might be able to use SB, and FF to use TB, but not other combinations. I can easily fudge OpenJDK/IcedTea to use Firefox for XUL, and fudge LibreOffice to use TB for it's address book integration. Same thing for libproxy, neon, VLC, etc. That means it can be done, but, it might make sense to put back the XUL compatibility pc files for FF if XUL is removed so that we don't have to jump through hoops for the current packages. Again, I haven't looked at it in some time, so this is all assuming that the maintainers haven't done this already. -- DJ Lucas -- This message has been scanned for viruses and dangerous content, and is believed to be clean. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
