From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] [POC] common/hooks: move shlibs from common/shlibs to individual templates
Date: Wed, 23 Nov 2022 01:29:12 +0100 [thread overview]
Message-ID: <20221123002912.pCaab9wKOXS0vvkVeJ61xOCRc09Q_ueyJ267uFa_WcY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40698@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/pull/40698#issuecomment-1324399652
Comment:
> * currently every shlib has to be on its own line which can easily break with += and there can not be a whitespace at the beginning of the line
I think this could be solved by using some special char between each shlibname and version. `:` may not be a good idea if that's wanted for epoch later, but maybe `=` could work, e.g.:
```sh
shlibs="libfoo.so.1=1.1_2
libbar.so.3=1.0_1"
```
or maybe `=>` or `>=` or `>` could make sense
next prev parent reply other threads:[~2022-11-23 0:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 18:51 [PR PATCH] " paper42
2022-11-22 20:01 ` Duncaen
2022-11-23 0:27 ` classabbyamp
2022-11-23 0:29 ` classabbyamp [this message]
2022-11-23 0:32 ` classabbyamp
2022-12-30 17:23 ` [PR PATCH] [Updated] " paper42
2023-03-31 1:55 ` 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=20221123002912.pCaab9wKOXS0vvkVeJ61xOCRc09Q_ueyJ267uFa_WcY@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).