From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] auto-disable debug and multilib for bootstrap packages?
Date: Sat, 04 Feb 2023 14:22:38 +0100 [thread overview]
Message-ID: <20230204132238.zmyRLsEJg_rGKS61gH9YUdepO9Km2XgMpZFyb11MDhk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42069@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/42069#issuecomment-1416749732
Comment:
> We have no mechanism for actually tying debug/multilib packages to their parents and tend to leave behind stale debugs when we change the package tree even after manually removing the parents.
We have `source-revisions`:
```
$ xbps-query --regex -Rp source-revisions -s "^zlib:"
zlib-1.2.13_1: zlib:5f1d95b23c (https://repo-fastly.voidlinux.org/current)
zlib-devel-1.2.13_1: zlib:5f1d95b23c (https://repo-fastly.voidlinux.org/current)
zlib-dbg-1.2.13_1: zlib:5f1d95b23c (https://repo-fastly.voidlinux.org/current/debug)
zlib-32bit-1.2.13_1: zlib:91837caec7 (https://repo-fastly.voidlinux.org/current/multilib)
zlib-devel-32bit-1.2.13_1: zlib:91837caec7 (https://repo-fastly.voidlinux.org/current/multilib)
```
We could also use that as a better way to delete packages in the future, instead of having file names we just have arch+source-revisions combos that we put in a script that looks up the packages and deletes them.
> If they end up in a bootstrap/debug repo, it's just another directory with a state that will deviate from the master. I can't imagine there's any real utility in the packages, so it's probably better to just skip them.
They should end up there IMHO, adding magic to disable debug based on repository just because there might be no apparent utility doesn't seem like a good idea. Seems like a bug that is only using the templates `repository` for the the package itself and multilib, but not for debug.
next prev parent reply other threads:[~2023-02-04 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 2:31 [ISSUE] " classabbyamp
2023-02-04 2:34 ` ahesford
2023-02-04 12:14 ` Duncaen
2023-02-04 13:07 ` ahesford
2023-02-04 13:22 ` Duncaen [this message]
2023-05-06 1:49 ` github-actions
2023-08-10 1:52 ` github-actions
2023-08-25 1:44 ` [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=20230204132238.zmyRLsEJg_rGKS61gH9YUdepO9Km2XgMpZFyb11MDhk@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).