From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH 1/2] GeoIP: add recipe
Date: Mon, 5 Jan 2015 14:22:47 -0500 [thread overview]
Message-ID: <20150105192246.GA28725@mentor.com> (raw)
In-Reply-To: <54AA23B3.6010001@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 6930 bytes --]
[Re: [oe] [meta-networking][PATCH 1/2] GeoIP: add recipe] On 15.01.05 (Mon 13:40) Robert Yang wrote:
>
>
> On 01/05/2015 01:36 PM, Lei, Maohui wrote:
> > Hi Robert
> >
> >
> >>> +HOMEPAGE = "http://dev.maxmind.com/geoip/"
> >>> +SECTION = "Development/Libraries"
> >>
> >> I think that this is a fedora like section name? We usually use debian style
> >> in OE, for example:
> >>
> >> SECTION = "net"
> >
> > Thank you, it does make sense. I didn't pay attention to this detail.
> > But it is hard to find the rule of assignment of " SECTION " variable.
> > I searched the meta-openembedded, "network" is also be used to be section name.
> > What's the difference between the "net" and the "network"?
>
> I think they are the same, Joe M, who is the maintainer of meta-networking may
> know about it.
I'm not aware of a stated policy on what format SECTION should follow or
what options are recommended, actually. At least in terms of
meta-networking I've not really questioned anything (as far as I know)
that looks sensible.
Now that I'm thinking about it, though, I think some sort of structure
would be good. So to that end, I won't ask for any changes here, but
I'll follow up (later on today, I hope) with my proposed changes to the
meta-networking hierarchy and hopefully get some kind of pattern to
what's set there. Right now a raw count shows the Fedora-style
convention is the most popular by a slim margin. I'm inclined to go
with, for example, SECTION = "console/network" here, since that conveys
a reasonable amount of information and looks to be easily parsable and
more closely matches what's used in, for example, meta-oe/.
-J.
>
> // Robert
>
> >
> > [meta-openembedded]$ grep "SECTION " ./ -r | grep bb
> > ...
> > ./meta-networking/recipes-connectivity/polarssl/polarssl_1.3.8.bb:SECTION = "net"
> > ...
> > ./meta-networking/recipes-daemons/squid/squid_3.4.7.bb:SECTION = "network"
> > ...
> > [meta-openembedded]$
> >
> >>
> >> The similar to geoipupdate.
> >
> >
> > Lei
> >
> >
> >
> >> -----Original Message-----
> >> From: openembedded-devel-bounces@lists.openembedded.org
> >> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
> >> Robert Yang
> >> Sent: Monday, January 05, 2015 11:07 AM
> >> To: openembedded-devel@lists.openembedded.org
> >> Subject: Re: [oe] [meta-networking][PATCH 1/2] GeoIP: add recipe
> >>
> >>
> >>
> >> On 01/05/2015 10:39 AM, leimaohui wrote:
> >>> From: leimh <leimaohui@cn.fujitsu.com>
> >>>
> >>> GeoIP app allow you to look up information about a given IP address.
> >>>
> >>> Signed-off-by: leimh <leimaohui@cn.fujitsu.com>
> >>> ---
> >>> .../recipes-support/geoip/geoip_1.6.0.bb | 58
> >> ++++++++++++++++++++++
> >>> 1 file changed, 58 insertions(+)
> >>> create mode 100644
> >>> meta-networking/recipes-support/geoip/geoip_1.6.0.bb
> >>>
> >>> diff --git a/meta-networking/recipes-support/geoip/geoip_1.6.0.bb
> >>> b/meta-networking/recipes-support/geoip/geoip_1.6.0.bb
> >>> new file mode 100644
> >>> index 0000000..d1bdae9
> >>> --- /dev/null
> >>> +++ b/meta-networking/recipes-support/geoip/geoip_1.6.0.bb
> >>> @@ -0,0 +1,58 @@
> >>> +SUMMARY = "C library for country/city/organization to IP address or hostname
> >> mapping"
> >>> +DESCRIPTION = "GeoIP is a C library that enables the user to find the
> >>> +country that any IP\ address or hostname originates from. It uses a
> >>> +file based database that is\ accurate as of March 2003. This database
> >>> +simply contains IP blocks as keys, and\ countries as values. This
> >>> +database should be more complete and accurate than\ using reverse DNS
> >> lookups."
> >>> +
> >>> +HOMEPAGE = "http://dev.maxmind.com/geoip/"
> >>> +SECTION = "Development/Libraries"
> >>
> >> I think that this is a fedora like section name? We usually use debian style
> >> in OE, for example:
> >>
> >> SECTION = "net"
> >>
> >> The similar to geoipupdate.
> >>
> >> // Robert
> >>
> >>> +
> >>> +SRC_URI =
> >> "http://www.maxmind.com/download/geoip/api/c/GeoIP-1.6.0.tar.gz;name=tarba
> >> ll \
> >>> +
> >> http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.da
> >> t.gz;apply=no;name=GeoIP-dat \
> >>> +
> >> http://geolite.maxmind.com/download/geoip/database/GeoIPv6.dat.gz;apply=no
> >> ;name=GeoIPv6-dat \
> >>> +
> >> http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz;appl
> >> y=no;name=GeoLiteCity-dat \
> >>> +
> >>>
> >> +http://geolite.maxmind.com/download/geoip/database/GeoLiteCityv6-beta/Geo
> >> LiteCityv6.dat.gz;apply=no;name=GeoLiteCityv6-dat \ "
> >>> +
> >>> +SRC_URI[tarball.md5sum] = "89f4cdfdab43f1d67364cd7c85bbe8ca"
> >>> +SRC_URI[tarball.sha256sum] =
> >> "075a0c2815cd099e9ec35c9569db716a3fefcdbb6a10dbfa1ce7c6cd48d4a635"
> >>> +
> >>> +SRC_URI[GeoIP-dat.md5sum] = "53416cd33e556a8048ac522fc9a98e05"
> >>> +SRC_URI[GeoIP-dat.sha256sum] =
> >> "a423a0c87bf9a78ef8d68153b424987c6bbddec85b5f784ca747706f4df10361"
> >>> +
> >>> +SRC_URI[GeoIPv6-dat.md5sum] = "f1a4abf4015c0300267f4717c9d7ead2"
> >>> +SRC_URI[GeoIPv6-dat.sha256sum] =
> >> "1a8e61732e39ac9d9acc20d648b2530d7bd0ff1c250f51fd18148931fbfe2830"
> >>> +
> >>> +SRC_URI[GeoLiteCity-dat.md5sum] = "48af3b8a204d7c5f8e42a4f5f4dd1874"
> >>> +SRC_URI[GeoLiteCity-dat.sha256sum] =
> >> "2f3f62f171c333cdd4e68534585e51978cb3a12dc7b269786f50daf10071d7d6"
> >>> +
> >>> +SRC_URI[GeoLiteCityv6-dat.md5sum] = "a42504adfd8030c3a10f749191598b4a"
> >>> +SRC_URI[GeoLiteCityv6-dat.sha256sum] =
> >> "4a5eeaa4a9107e6ccdbe94ad1c7c987dc70cd250cd40624ada1e3a03836bbbdb"
> >>> +
> >>> +
> >>> +LICENSE = "LGPL-2.1"
> >>> +
> >>> +LIC_FILES_CHKSUM = "file://COPYING;md5=d5d53d6b948c064f4070183180a4fa89 \
> >>> + file://LICENSE;md5=f04db71812ba70aaba8b38da91984cd2
> >> "
> >>> +
> >>> +S = "${WORKDIR}/GeoIP-1.6.0"
> >>> +
> >>> +inherit autotools
> >>> +
> >>> +EXTRA_OECONF = "--disable-static \
> >>> + --disable-dependency-tracking "
> >>> +
> >>> +do_install() {
> >>> + make DESTDIR=${D} install
> >>> + install -d ${D}/${datadir}/GeoIP
> >>> + install ${WORKDIR}/GeoIP.dat ${D}/${datadir}/GeoIP/
> >>> + install ${WORKDIR}/GeoIPv6.dat ${D}/${datadir}/GeoIP/
> >>> + install ${WORKDIR}/GeoLiteCity.dat ${D}/${datadir}/GeoIP/
> >>> + install ${WORKDIR}/GeoLiteCityv6.dat ${D}/${datadir}/GeoIP/ }
> >>> +
> >>> +PACKAGES =+ "${PN}-database"
> >>> +FILES_${PN}-database = ""
> >>> +FILES_${PN}-database += "${datadir}/GeoIP/*"
> >>> +
> >>>
> >> --
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> >
> >
--
-Joe MacDonald.
:wq
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 501 bytes --]
next prev parent reply other threads:[~2015-01-05 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 2:39 [meta-networking][PATCH 0/2] add new recipes for GeoIP leimaohui
2015-01-05 2:39 ` [meta-networking][PATCH 1/2] GeoIP: add recipe leimaohui
2015-01-05 3:06 ` Robert Yang
2015-01-05 5:36 ` Lei, Maohui
2015-01-05 5:40 ` Robert Yang
2015-01-05 19:22 ` Joe MacDonald [this message]
2015-01-05 2:39 ` [meta-networking][PATCH 2/2] geoipupdate: add new recipe leimaohui
2015-01-07 19:13 ` [meta-networking][PATCH 0/2] add new recipes for GeoIP Joe MacDonald
-- strict thread matches above, loose matches on Subject: below --
2014-12-26 6:23 leimaohui
2014-12-26 6:23 ` [meta-networking][PATCH 1/2] GeoIP: add recipe leimaohui
2014-12-30 8:27 ` Martin Jansa
2015-01-02 11:18 ` Lei, Maohui
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=20150105192246.GA28725@mentor.com \
--to=joe_macdonald@mentor.com \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.