Dear all,
I'm a bit late to the party, but here is my $0.02:
REQUIRED_USE=
curl_ssl_winssl? ( elibc_Winnt )
ssl? (
^^ (
[...]
)
)
I don't like this. If the user specifies several SSL providers in
make.conf, it should mean that any of these is fine and the
On 06/11/14 07:12, Chí-Thanh Christopher Nguyễn wrote:
Dear all,
I'm a bit late to the party, but here is my $0.02:
REQUIRED_USE=
curl_ssl_winssl? ( elibc_Winnt )
ssl? (
^^ (
[...]
)
)
I don't like this. If the user specifies several SSL providers in
Dnia 2014-06-11, o godz. 13:12:38
Chí-Thanh Christopher Nguyễn chith...@gentoo.org napisał(a):
REQUIRED_USE=
curl_ssl_winssl? ( elibc_Winnt )
ssl? (
^^ (
[...]
)
)
I don't like this. If the user specifies several SSL providers in
make.conf, it
Michał Górny schrieb:
I don't like this. If the user specifies several SSL providers in
make.conf, it should mean that any of these is fine and the ebuild can
choose an arbitrary one. The exactly-one-of operator would cause emerge
to complain in this case and possibly force the user to have
Dnia 2014-06-11, o godz. 15:30:26
Chí-Thanh Christopher Nguyễn chith...@gentoo.org napisał(a):
3. There is no clean way of enforcing SSL provider match between
packages. Wasn't this thread initially about curl and rtmpdump
requiring matching flags?
It could be enforced if an eclass does
Michał Górny schrieb:
Dnia 2014-06-11, o godz. 15:30:26
Chí-Thanh Christopher Nguyễn chith...@gentoo.org napisał(a):
3. There is no clean way of enforcing SSL provider match between
packages. Wasn't this thread initially about curl and rtmpdump
requiring matching flags?
It could be enforced
On Thu, 29 May 2014 13:42:01 -0400
Anthony G. Basile bluen...@gentoo.org wrote:
Back in Jun 2012 I added a CURL_SSL to the USE_EXPAND to represent
You could start by fixing boring old bugs instead of working on
exciting new features. See bug 510580, née 499398, which stops everyone
from
Hi everyone,
Back in Jun 2012 I added a CURL_SSL to the USE_EXPAND to represent the
different ssl providers for curl. This was to get away from the old ssl
USE flag logic which you still see in packages like
media-video/rtmpdump. Quoting from there so you don't have to go find it
yourself
Anthony G. Basile wrote:
2. migrate curl and all its dependencies to the SSL use expand.
3. Migrate over all consumers of ssl to the new SSL use expand system.
As long as consumers can support only a few of the expansions that
just seems to tidy things up, which is a good thing.
//Peter
