From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2 1/2] geoip: new package
Date: Mon, 23 Jun 2014 13:59:51 -0300 [thread overview]
Message-ID: <53A85D07.3070802@zacarias.com.ar> (raw)
In-Reply-To: <20140623163845.GA3400@free.fr>
On 06/23/2014 01:38 PM, Yann E. MORIN wrote:
>> Geoipupdate is for commercial users AFAIK, i have no such access/account
>> to test the package. You need to configure a maxmind user/password to
>> make it work, it's not an out-of-the-box experience.
>
> Well, I don't see where the problem lies. There's nothing that prevents
> us from packaging geoipupdate, even if it requires a runtime
> configuration with a login+password.
>
> That's basically the same as for a webserver: we do package more than
> one webserver, but the user is still responsible for providing the
> content of the server-root.
I disagree a bit there, but then people are free to do what they like,
like shipping a probably toughly-licensed user/pass combination in
plaintext in a firmware which someone else can pick up and use let's say
in shady terms :)
It's mostly intended for servers where access is restricted and that
wouldn't happen normally.
>> Someone who has might be interested to make it though.
>
> I agree with you on that. ;-)
I like to test new packages a bit, and getting the help just doesn't
feel like a proper test, hence my reluctance ;)
Regards.
prev parent reply other threads:[~2014-06-23 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 14:39 [Buildroot] [PATCHv2 1/2] geoip: new package Gustavo Zacarias
2014-06-17 14:39 ` [Buildroot] [PATCHv2 2/2] php-geoip: " Gustavo Zacarias
2014-06-22 19:55 ` Thomas Petazzoni
2014-06-22 19:54 ` [Buildroot] [PATCHv2 1/2] geoip: " Thomas Petazzoni
2014-06-22 22:34 ` Gustavo Zacarias
2014-06-22 22:40 ` Yann E. MORIN
2014-06-22 22:47 ` Gustavo Zacarias
2014-06-23 16:38 ` Yann E. MORIN
2014-06-23 16:59 ` Gustavo Zacarias [this message]
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=53A85D07.3070802@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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