From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Issue with automake 1.16.4+ and python
Date: Sun, 17 Oct 2021 15:02:36 +0200 [thread overview]
Message-ID: <20211017130236.TV44byA4Vtm3EdsTu6I0k7cyPhU3jTeRvzBqDFbV94s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33559@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/33559#issuecomment-945116914
Comment:
The ugliest part about this is that they decided to use variable names that look totally different from other variables in the pc files, which makes the intention harder to gather. Why not `pyexecprefix` and `pyprefix` To make it clear these should be set like others? For that matter, why does `PYTHON_EXEC_PREFIX` even exist? What does this provide that can't be discerned by `pyexecdir`?
At this point, drop the patch in this PR since they clearly don't want the old behavior. I think whatever this breaks should be fixed by attrition; adding an xbps-src hook to scan pc files will add extra time to package building for little benefit. Presumable other upstreams will fix this problem in due time, and we can patch what we identify in the meantime.
next prev parent reply other threads:[~2021-10-17 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 8:36 [ISSUE] " newbluemoon
2021-10-16 19:00 ` ahesford
2021-10-16 19:21 ` newbluemoon
2021-10-16 19:25 ` ahesford
2021-10-16 19:41 ` newbluemoon
2021-10-16 19:48 ` newbluemoon
2021-10-17 5:57 ` newbluemoon
2021-10-17 7:00 ` newbluemoon
2021-10-17 13:02 ` ahesford [this message]
2021-10-17 14:48 ` newbluemoon
2022-06-08 2:12 ` github-actions
2022-06-22 2:13 ` [ISSUE] [CLOSED] " github-actions
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=20211017130236.TV44byA4Vtm3EdsTu6I0k7cyPhU3jTeRvzBqDFbV94s@z \
--to=ahesford@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).