Hello, I use: mozilla-1.7 from portage tree Extensions: Extensions don't matter on this issue. The issue: I set the local USE flag "moznocompose" but composer got compiled in. When looking into the ebuild I found the reason -- it only takes affect in case of moznomail being set as well. First of all this dependancy isn't documented in use.local.desc: net-www/mozilla:moznocompose - Disable building of mozilla's web page composer net-www/mozilla:moznomail - Disable building mozilla's mail client From this information I would never have thought of any effect of "moznomail" on "moznocompose". Second this dependancy doesn't show up in the configure script of mozilla source itself: --disable-mailnews Disable building of mail & news components --disable-composer Disable building of Composer So there is no need to create this dependancy on ebuild level. Third there is another option in the configure script: --enable-plaintext-editor-only Allow only plaintext editing This tells me that there is no connection between the two afore mentioned options. Reproducible: Always Steps to Reproduce: 1. Search in /usr/portage/profiles/use.local.desc for "mozilla" 2. Search in /usr/portage/net-www/mozilla/mozilla-1.7.ebuild for "moznocompose" 3. Use --help option on ./configure script provided with mozilla sources Actual Results: composer gets build despite of moznocompose flag set. Expected Results: composer should not be build. I will submit a new bug report regarding the third option I mentioned here. These two may be worked on in one go.
Created attachment 34579 [details, diff] a small patch to get rid of dependancy
Ok, I learned within the last two days that one can build a mail client without being able to write any mail (though one has to start mozilla with the --mail invocation option). So a fully functioning mail client really depends on composer. So my bug report needs a change: - no changes within the ebuild - correction in use.local.desc: "web page composer" is wrong and please mention dependency - bug report to upstream: they should at least mention the dependancy. bye caspar
Unless it's changed, --disable-composer disables building the HTML editor component of the Mozilla suite, which means our description in use.local.desc is correct. As far as our description goes it's still correct, but it is definitely worthy of being mentioned upstream. Going to mark this wontfix since the stuff on our side is otherwise as it should be. Thanks for the input though!
First of all this bug is a duplicate of #24401. Second the description doesn't tell it's the "html editor component" but the "web page editor". If that component is used to compose mails it's not a web page editor but a general editor. And for I write all my mails in plaintext mode I wouldn't see any dependancy if it was called "html editor". So you replace one ambiguous term with another ambiguous term. I use this program and for that I don't need to know by myself which components depend on each other internally. It's upstreams part to provide that information to distributors and those who compile the sources directly. They weren't clear about that. And it's the distributors' part to work on that. You did so by writing the ebuild accordingly, the dependancy is coded there. That is great. But you didn't tell the ones who use the flags about that. I got mislead a few days before. A few months ago others had the same problem with mozilla 1.4 and 1.5. Even upstream has a bug report on that issue. It just isn't clear.
