From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [proposal] templates without official binaries
Date: Tue, 27 Oct 2020 12:53:47 +0100 [thread overview]
Message-ID: <20201027115347.Cv0vTVDbg7HimU9OLuBaOAOI_wPxIqEqCKDz9J5E3Sg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25901@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/25901#issuecomment-717191594
Comment:
We already have that with restricted packages, mainly for things we are not allowed to redistribute.
A major problem with that is that its becomes a lot harder to check if changes don't break the currently limited amount of restricted packages.
Without binary packages in a repository, there is no fast way to look up what libraries a restricted package links, resulting in situations where a seemingly harmless change like removing a [libcurl-gnutls.so symlink](https://github.com/void-linux/void-packages/pull/25764) and then accidentally [breaking restricted packages like spotify](https://github.com/void-linux/void-packages/commit/1c81540ce821e58faa240d7a0428d90ae480f96f).
Its similar for dependencies, with packages in the repository we can go through the repository metadata and see all packages depending on another package, with restricted packages this information is limited to template files, which are not easy to parse and change depending on outside factors like the architecture meaning you have to evaluate every single template file to gather dependencies.
next prev parent reply other threads:[~2020-10-27 11:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 15:53 [ISSUE] " hippi777
2020-10-27 11:53 ` Duncaen
2020-10-27 11:53 ` Duncaen [this message]
2020-10-27 13:20 ` hippi777
2020-10-31 16:58 ` reback00
2020-10-31 17:23 ` hippi777
2020-10-31 17:47 ` reback00
2020-11-01 9:56 ` hippi777
2020-11-01 10:29 ` Duncaen
2020-11-01 11:45 ` hippi777
2020-11-01 12:05 ` Duncaen
2020-11-01 12:06 ` Duncaen
2020-11-01 18:13 ` reback00
2020-11-01 18:14 ` reback00
2020-11-01 18:17 ` reback00
2020-11-01 20:06 ` hippi777
2020-11-01 22:31 ` fosslinux
2020-11-01 22:34 ` fosslinux
2020-11-02 16:12 ` reback00
2022-04-22 2:14 ` github-actions
2022-04-22 15:56 ` [ISSUE] [CLOSED] " Duncaen
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=20201027115347.Cv0vTVDbg7HimU9OLuBaOAOI_wPxIqEqCKDz9J5E3Sg@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).