Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] libgdal - Please update package and enable python bind
Date: Sat, 05 Nov 2022 08:42:09 +0100	[thread overview]
Message-ID: <20221105074209.T8c4M_vWzqUoFnf6q47ZptnAPFGE10W7UKjogR3ipy8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36816@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

Closed issue by gabriel-russo on void-packages repository

https://github.com/void-linux/void-packages/issues/36816

Description:

## Update
Please, update package libgdal and subpackages from 3.0.4 (released in 2020-01-28) to 3.4.2 (current release)

## Feature
According to [Pypi GDAL page](https://pypi.org/project/GDAL/#building-as-part-of-the-gdal-library-source-tree) you can also have the GDAL Python bindings built as part of a source build by specifying `--with-python` as part of your configure line. 

If it's possible, make a Configure option to enable python bindings build in libgdal package.

## Python bind in libgdal-3.0.4 template


` # Template file for 'libgdal'`
...
`configure_args=" ... --with-python"`
`makedepends="... python-devel python-setuptools"`
`python_version=2`
...
For some reason i can't put it working with python3, any future success i will report it here.




      parent reply	other threads:[~2022-11-05  7:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22 18:12 [ISSUE] " gabriel-russo
2022-04-22 20:03 ` Chocimier
2022-04-22 22:18 ` gabriel-russo
2022-04-23  0:32 ` classabbyamp
2022-07-22  2:13 ` github-actions
2022-07-27  9:52 ` ar-jan
2022-07-27  9:55 ` sgn
2022-10-27  2:13 ` github-actions
2022-11-05  7:27 ` kruceter
2022-11-05  7:28 ` kruceter
2022-11-05  7:42 ` classabbyamp [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=20221105074209.T8c4M_vWzqUoFnf6q47ZptnAPFGE10W7UKjogR3ipy8@z \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).