I was really sick of having nss and nspr installed additionally to firefox and so I added my firefox to evolution's fan-list. :) Reusing the firefox USE-tag.
Created attachment 56360 [details] firefox based evolution dataserver
Created attachment 56361 [details] Evolution based on firefox
Qui: If you attach something, a unified diff is preferred. The header is invalid, please read http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=3
You could have saved your comment and replace the header. Maybe you can file a bug report for my "faulty" header :rolleyes:
Can it get into portage ?
besides, evolution 2.2.3 is out: http://ftp.gnome.org/pub/GNOME/sources/evolution/2.2/evolution-2.2.3.news
If you want 2.2.3 then replace the version in the ebuild's name appropriately. The ebuilds will still work and download the newest version.
Maintainability using nested !<package>? conditionals becomes increasingly flakey. Maybe using the following will help to simplify things a bit (I've tested this successfully on my system for many packages): ssl? ( || ( mozilla? ( www-client/mozilla ) mozilla-firefox? ( www-client/mozilla-firefox ) ( >=dev-libs/nspr-4.4.1 >=dev-libs/nss-3.9.2 ) ) ) Then, on the command-line you can use any of the following: Emerge evolution using mozilla-firefox: USE="+mozilla-firefox" emerge evolution Emerge evolution using nspr and nss: USE="-mozilla-firefox -mozilla" emerge evolution Emerges evolution using mozilla: USE="-mozilla-firefox +mozilla" emerge evolution
Created attachment 61893 [details, diff] Patch to add Firefox support and fix outdated URL for Evolution homepage 1. Uses ||() conditional, instead of many nested !<package>? conditionals. 2. Updated the new Evolution homepage on Novell's website.
Great work! This looks stable to me, which can be merged into portage. Nonetheless I don't like 'mozilla-firefox' as USE-Flag. The epiphany-ebuilds used 'firefox'.
Created attachment 61902 [details, diff] Patch to support evolution-data-server using firefox nspr-headers Evolution-Data-Server ebuild diff for use with firefox nspr/nss suite. Usage as above, but includes 'firefox'-useflag. You also need the firefox-ebuild, that supports nspr/nss headers, which can be obtained here: http://bugs.gentoo.org/show_bug.cgi?id=86070
(In reply to comment #10) > Great work! This looks stable to me, which can be merged into portage. > Nonetheless I don't like 'mozilla-firefox' as USE-Flag. The epiphany-ebuilds > used 'firefox'. I used 'mozilla-firefox' because the Firefox package is called 'mozilla-firefox'. I used it for consistency with the portage tree.
I don't see the sense of this illusionary building against sth. After all, how could someone be sure that at run-time this will link against firefox or mozilla, most probably on majority installations with this 10MozillaFirefox hack in /etc/env.d all libraries will resolve to firefox. You could try it very simply ldd /usr/lib/evolution/2.2/libeutil.so.0.0.0, build with firefox support try again, build it with mozilla support try again and with standard support and again. You will be bemused, it will always link against what stays on top of ld.so.conf. The ebuild should set the RPATH/RUNPATH tags to secure the runtime linking (I think), otherwise it is simply a game of poker.
What you say does not make sense. I build against firefox' nspr-suite to save me from installing the separate nss/nspr-suite. It does not link what is available. It links what I tell configure to use and so it works. You don't need to use it, why do you complain at all? Most others are happy...
Don't take me bad :) Probably your way is the most correct (in the sense, what the remark was meant to be understand), but altogether it is the unreliable way of doing it. There are also some bugs in your firefox-build (installing the binaries from firefox nss/nspr collide with mozilla, and I don't think they are needed for the evolution or evolution-data-server). You could look at the group of ebuilds at bug #100597, to see what I mean with all this.
Yes, it actually is. Nonetheless do us a favor and stop creating duplicate threads for everything that we do here. If you're not satisfied then create a diff or new ebuild and post it into existing bugreports. Don't forget to give arguments for your changes or they will certainly be ignored. Also I don't recommend compiling against mozilla or firefox only but include the nss/nspr package as well. Don't say there are bugs but tell us where the bugs are.
Created attachment 66910 [details, diff] evolution-2.3.8-r1.diff This diff extends the current (evolution-2.3.8) ebuild to compile against firefox' ssl.
Created attachment 66911 [details, diff] evolution-data-server-1.3.7-r1.diff Same for evolution data server.. SSL bla ble...
The nss headers will not be installed with firefox. We are gonna be removing the mozilla nss headers from the ebuild shortly as well, this is gonna force all packages that need nss/nspr to build against in tree packages and not against firefox/mozilla.
closing as won't fix per mozilla teams decision to removie nss stuff from firefox ebuilds
Don't you think you are repeating nonsense way to much??
