Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: common/shlibs: add shlibs for simavr
Date: Mon, 19 Oct 2020 17:57:14 +0200	[thread overview]
Message-ID: <20201019155714.PcrlDfhx3v2lEWPgyFWS9Azshwrw5flglpzSYSoZ9gk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25741@inbox.vuxu.org>

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

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/pull/25741#issuecomment-712263185

Comment:
> Can someone explain why do we need to add shlibs manually?
> How hard is to automate this process?

It records the first version a shared library was introduced to create dependencies like `librarypkg>=firstversion`.
Automating it by using repository metadata would introduce state that depends on the build history so its not reproducible anymore and depending on the history or your local xbps repository the dependencies would differ from the build servers history.
Automatically changing tracked files when running xbps-src is also not that nice and would probably lead to more issues than changing the file manually if required.

  parent reply	other threads:[~2020-10-19 15:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 15:25 [PR PATCH] " Logarithmus
2020-10-19 15:39 ` sgn
2020-10-19 15:55 ` Duncaen
2020-10-19 15:57 ` Duncaen [this message]
2020-10-20  0:32 ` ahesford
2020-10-20  0:32 ` [PR PATCH] [Closed]: " ahesford

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=20201019155714.PcrlDfhx3v2lEWPgyFWS9Azshwrw5flglpzSYSoZ9gk@z \
    --to=duncaen@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).