Github messages for voidlinux
 help / color / mirror / Atom feed
From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: grass: update to 8.3.0, orphan
Date: Wed, 27 Sep 2023 13:15:09 +0200	[thread overview]
Message-ID: <20230927111509.d423F2BqcEWm10Jm5dZyoRXfynan_QIgN-EbuV7TPT0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46285@inbox.vuxu.org>

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

New comment by ar-jan on void-packages repository

https://github.com/void-linux/void-packages/pull/46285#issuecomment-1737189909

Comment:
Great, works for me! I don't use the grass gui myself either but it seems to work.

For my understanding, where you're patching `grass.pc.in` I'd tried to address this with

``` sh
post_configure() {
	vsed -i grass.pc -e "s|/usr/lib/grass-$version|/usr/lib/grass$_binver|g"
}
```

So that must've been the reason the libraries weren't found, is that expected not to work? (I did use shlib_provides etc.)

Also wondering, what's the reason to move the symlinks in lib to the -devel package? (when the versioned .so files stay in the main package)

For use with QGIS: would it make more sense to just use `/usr/lib/grass` as install location, instead of `/usr/lib/grass${_binver}`, so we don't have to hardcode the library version in the QGIS template? (It would be nice if we could do `-DGRASS_PREFIX8=$(pkg-config --variable=prefix grass)` but that isn't supported, could it be?).

  parent reply	other threads:[~2023-09-27 11:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27  6:40 [PR PATCH] " classabbyamp
2023-09-27  7:20 ` [PR PATCH] [Updated] " classabbyamp
2023-09-27 11:12 ` ar-jan
2023-09-27 11:15 ` ar-jan [this message]
2023-09-27 18:09 ` classabbyamp
2023-09-27 18:48 ` [PR PATCH] [Updated] " classabbyamp
2023-09-27 18:49 ` classabbyamp
2023-09-27 20:01 ` [PR PATCH] [Merged]: " classabbyamp

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=20230927111509.d423F2BqcEWm10Jm5dZyoRXfynan_QIgN-EbuV7TPT0@z \
    --to=ar-jan@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).