From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 32813@debbugs.gnu.org
Subject: [bug#32813] [PATCH 3/4] gnu: Add osm2pgsql.
Date: Tue, 25 Sep 2018 19:37:40 +0200 [thread overview]
Message-ID: <20180925193740.0284e415@alma-ubu> (raw)
In-Reply-To: <20180923204311.8086-3-julien@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
On Sun, 23 Sep 2018 22:43:10 +0200
Julien Lepiller <julien@lepiller.eu> wrote:
> * gnu/packages/geo.scm (osm2pgsql): New variable.
> ---
> gnu/packages/geo.scm | 30 ++++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/gnu/packages/geo.scm b/gnu/packages/geo.scm
> index 81bffcc88..efc68ea85 100644
> --- a/gnu/packages/geo.scm
> +++ b/gnu/packages/geo.scm
> @@ -824,3 +824,33 @@ delivered to any client.")
> files and imports the data into PostgreSQL/PostGIS databases. It is
> designed to create databases that are optimized for
> rendering/tile/map-services.") (license license:asl2.0)))
> +
> +(define-public osm2pgsql
> + (package
> + (name "osm2pgsql")
> + (version "0.96.0")
[..]
> + (license license:gpl2)))
Hm.
The COPYING file says gpl2.
The README is saying nothing about the license. A LICENSE file is
missing.
Most .cpp/.h files do not have a header and do not clarify it.
But these 3 do:
./parse-osmium.cpp: *No copyright* GPL (v2 or later)
./parse-osmium.hpp: *No copyright* GPL (v2 or later)
./tests/test-options-projection.cpp: GPL (v2 or later)
Is this (list gpl2 gpl2+) ?!
Found more:
./contrib/protozero/LICENSE.from_folly: *No copyright* Apache License (v2.0)
./contrib/protozero/LICENSE.md: BSD 2-clause "Simplified" License
./contrib/libosmium/osmium/*: BSL
Does it make sense/have you tried to
unbundle protozero and libosmonium:
https://github.com/mapbox/protozero
https://github.com/osmcode/libosmium
Either unbundle or add to copyright line.
Missing import:
#:use-module (gnu packages lua)
Otherwise, LGTM
Thanks,
Björn
--
Dipl.-Inf. Björn Höfling
Software Developer (GIS, Java)
http://www.bjoernhoefling.de/
+49-176-666 875 06
USt-IdNr: DE275885245
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-09-25 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 20:39 [bug#32813] [PATCH] OSM-related packages Julien Lepiller
2018-09-23 20:43 ` [bug#32813] [PATCH 1/4] gnu: Add tegola Julien Lepiller
2018-09-23 20:43 ` [bug#32813] [PATCH 2/4] gnu: Add imposm3 Julien Lepiller
2018-09-25 17:16 ` Björn Höfling
2018-09-23 20:43 ` [bug#32813] [PATCH 3/4] gnu: Add osm2pgsql Julien Lepiller
2018-09-25 17:37 ` Björn Höfling [this message]
2018-09-25 17:39 ` Björn Höfling
2018-09-23 20:43 ` [bug#32813] [PATCH 4/4] gnu: Add tippecanoe Julien Lepiller
2018-09-25 17:52 ` Björn Höfling
2018-09-25 17:04 ` [bug#32813] [PATCH 1/4] gnu: Add tegola Björn Höfling
2018-09-29 10:47 ` [bug#32813] [PATCH] OSM-related packages Julien Lepiller
2018-09-29 12:11 ` bug#32813: " Julien Lepiller
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180925193740.0284e415@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=32813@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).