Hi Ricardo, first of all, thanks for responding. This discussion is perhaps academic but for me the underlining principle we are discussing is that the packager should be in control of the package. For the specifics of this case, you have the control over your package, but you don't over what libetpan did, does, or will do. In my opinion, if a certain culr ssl variant is needed for the plugins to compile and work, or because you have chosen, or are obliged to choose, to license the package with a certain license, you should impose this and not rely on libetpan to do it in accordance with your wishes.
>any plugin not liking the libetpan's provided choice for curl >SSL library variant would FTBS, the same as if you explicitly force the >dependency and libetpan wants other (IIRC you can't have both), so I don't >see the point of adding it. If you specify one and libetpan another and there is an FTBFS that's a good sign that you have to check whats going on. >OTOH if plugin builds happily with any curl SSL choice but you force one >against libetpan requirements you'll have a spurious FTBS, so this is a >strong point against adding it :) Again, in my mind this is a good point in having it, it will be a good warning that one has to check why it FTBFS and react accordingly. Cesare -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
