From: heliocat <heliocat@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: runit-void: split package into main package and init controls
Date: Mon, 01 Mar 2021 03:02:48 +0100 [thread overview]
Message-ID: <20210301020248.f6Pw4yS2715qq5F2p2zwbU1k7q_RtwCRvivQtzojxSA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29115@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
New comment by heliocat on void-packages repository
https://github.com/void-linux/void-packages/pull/29115#issuecomment-787584309
Comment:
> > First, someone (it might have even been you) had mentioned in IRC that xbps-alternatives was buggy and so I didn't want to put something as critical as startup and shutdown on that.
>
> Yes it was me. But virtual packages have similar issues too, and are generally avoided when possible. So I understand that committers would not want to take responsibilities for this.
>
> > The second is that I don't know at what point alternatives become available in the life of a new system
>
> The symlink should be there as soon as it is installed, so I don't see the issue here... but maybe I'm missing something.
>
> As a start it would be good to do what ahesford said and move away from `runit-void` things that should be elsewhere. The `ignorepkg` approach is better than nothing...
I've got a half written reply to aheford vis-a-vis moving away from runit-void but the gist of is that I agree but didn't want to break that work off as part of this, at least not as part of the initial PR. As for the symlink presence, the concern is really about the guarantees around when alternatives symlinks are present. The dependency graph guarantees that packages, and by extension binaries, will be present but I don't know if alternatives provide those same guarantees in all circumstances.
next prev parent reply other threads:[~2021-03-01 2:02 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 7:23 [PR PATCH] " heliocat
2021-02-28 7:26 ` heliocat
2021-02-28 9:14 ` st3r4g
2021-02-28 10:23 ` st3r4g
2021-02-28 11:13 ` st3r4g
2021-02-28 11:16 ` st3r4g
2021-02-28 12:52 ` teldra
2021-02-28 13:30 ` mobinmob
2021-02-28 15:53 ` ahesford
2021-02-28 19:50 ` heliocat
2021-02-28 22:07 ` st3r4g
2021-02-28 22:07 ` st3r4g
2021-02-28 23:05 ` st3r4g
2021-03-01 2:02 ` heliocat [this message]
2021-03-01 17:04 ` st3r4g
2021-03-02 1:00 ` heliocat
2021-03-02 23:17 ` [PR PATCH] [Updated] " heliocat
2021-03-03 8:54 ` heliocat
2021-03-03 15:01 ` leahneukirchen
2021-03-07 13:32 ` st3r4g
2021-03-07 20:06 ` heliocat
2021-03-08 1:08 ` st3r4g
2021-03-08 1:31 ` heliocat
2021-03-08 17:57 ` st3r4g
2021-03-08 18:02 ` st3r4g
2021-03-08 18:03 ` st3r4g
2021-03-09 1:12 ` heliocat
2021-03-09 6:34 ` [PR PATCH] [Updated] " heliocat
2021-03-09 6:34 ` heliocat
2021-03-09 6:35 ` heliocat
2021-03-09 6:35 ` heliocat
2021-03-12 17:41 ` st3r4g
2021-03-12 17:45 ` st3r4g
2021-03-12 22:36 ` heliocat
2021-03-14 0:41 ` [PR PATCH] [Updated] " heliocat
2021-03-14 0:44 ` heliocat
2021-03-14 0:45 ` heliocat
2021-03-14 4:14 ` [PR PATCH] [Updated] " heliocat
2021-03-14 18:49 ` heliocat
2021-03-14 18:54 ` heliocat
2021-03-17 17:08 ` [PR PATCH] [Updated] runit-void: add alternatives to runit-void to facilitate fast init switching heliocat
2021-03-17 18:04 ` heliocat
2021-03-20 7:28 ` heliocat
2021-04-03 22:09 ` [PR PATCH] [Updated] " heliocat
2021-04-10 17:11 ` Gottox
2021-04-13 7:11 ` heliocat
2021-06-23 18:09 ` [PR PATCH] [Updated] " heliocat
2022-05-05 2:09 ` github-actions
2022-05-19 2:15 ` [PR PATCH] [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=20210301020248.f6Pw4yS2715qq5F2p2zwbU1k7q_RtwCRvivQtzojxSA@z \
--to=heliocat@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).