From: Patrick Lauer <patrick@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New USE_EXPAND NGINX_MODULES_STREAM
Date: Tue, 9 Feb 2016 07:37:10 +0100 [thread overview]
Message-ID: <56B98916.809@gentoo.org> (raw)
In-Reply-To: <20160208235919.5e1cb56f@gentp.lnet>
On 02/08/2016 11:59 PM, Luis Ressel wrote:
> On Tue, 9 Feb 2016 11:34:12 +1300
> Kent Fredric <kentfredric@gmail.com> wrote:
>
>> nginx_modules_http_geoip? ( dev-libs/geoip )
>> nginx_modules_http_gunzip? ( sys-libs/zlib )
>> nginx_modules_http_gzip? ( sys-libs/zlib )
>> nginx_modules_http_gzip_static? ( sys-libs/zlib )
>> nginx_modules_http_image_filter? ( media-libs/gd[jpeg,png] )
>> nginx_modules_http_perl? ( >=dev-lang/perl-5.8 )
>> nginx_modules_http_rewrite? ( >=dev-libs/libpcre-4.2 )
>> nginx_modules_http_secure_link? (
>> userland_GNU? (
>> !libressl? ( dev-libs/openssl:0= )
>> libressl? ( dev-libs/libressl:= )
>> )
>> )
>> nginx_modules_http_xslt? ( dev-libs/libxml2 dev-libs/libxslt )
>> nginx_modules_http_lua? ( !luajit? ( dev-lang/lua:0= ) luajit?
>> ( dev-lang/luajit:2= ) )
>> nginx_modules_http_auth_pam? ( virtual/pam )
>> nginx_modules_http_metrics? ( dev-libs/yajl )
>> nginx_modules_http_dav_ext? ( dev-libs/expat )
>> nginx_modules_http_security? ( >=dev-libs/libxml2-2.7.8
>> dev-libs/apr-util www-servers/apache )
>> nginx_modules_http_auth_ldap? ( net-nds/openldap[ssl?] )
>>
> Thanks for citing this, I think it demonstrates mgorny's point rather
> nicely; we have global USE flags for many of those modules:
>
> * nginx_modules_http_perl -> perl
> * nginx_modules_http_auth_pam -> pam
> * nginx_modules_http_auth_ldap -> ldap
> * nginx_modules_http_geoip -> geoip
> * nginx_modules_http_g(un)zip -> zlib
> * nginx_modules_http_secure_link -> ssl
>
> The following two ones aren't quite as obvious, but could also be
> changed:
> * nginx_modules_http_rewrite -> pcre
> * nginx_modules_http_image_filter -> gd
>
> Introduce new USE flags for the remaining few modules -- voilà, there
> you go, no need for a new USE_EXPAND and the users will even get a
> useful set of default modules enabled based on their global USE flags.
>
And now I can't figure out what I need to enable to have "rewrite" work.
Good job!
The names match the internal module names, which is what I care about.
Figuring out if I need USE="zlib" or USE="compress" or even a combo is a
lot more effort and frustrating than having to enable the useflag that
has the name of the module.
It might not be 'pure' or very aesthetical, but we try to get stuff done
here.
next prev parent reply other threads:[~2016-02-09 6:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 22:29 [gentoo-dev] New USE_EXPAND NGINX_MODULES_STREAM Manuel Rüger
2016-02-03 22:48 ` Michał Górny
2016-02-04 10:03 ` Dirkjan Ochtman
2016-02-04 10:27 ` Jason Zaman
2016-02-04 12:01 ` Dirkjan Ochtman
2016-02-04 12:22 ` Alexis Ballier
2016-02-08 21:41 ` Michał Górny
2016-02-08 22:34 ` Kent Fredric
2016-02-08 22:44 ` James Le Cuirot
2016-02-08 22:56 ` Kent Fredric
2016-02-08 22:59 ` Luis Ressel
2016-02-08 23:22 ` Kent Fredric
2016-02-08 23:33 ` Luis Ressel
2016-02-09 6:37 ` Patrick Lauer [this message]
2016-02-09 8:18 ` Luis Ressel
2016-02-08 23:07 ` Luis Ressel
2016-02-04 12:17 ` Kent Fredric
2016-02-04 22:35 ` Gordon Pettey
2016-02-05 6:38 ` Jason Zaman
2016-02-05 11:07 ` Michał Górny
2016-02-06 20:08 ` Matt Turner
2016-02-04 10:14 ` Alexis Ballier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56B98916.809@gentoo.org \
--to=patrick@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox