From: Andy Tai <atai@atai.org>
To: guix-devel@gnu.org
Subject: Re: Request for assistance maintaining LibreWolf
Date: Sat, 17 Aug 2024 17:11:44 -0700 [thread overview]
Message-ID: <CAJsg1E_rNRKy0R2YuH+vETQz6Lb-9tvjHQg+4KH2vhb0wYvsDQ@mail.gmail.com> (raw)
In-Reply-To: <mailman.5970.1723926982.21382.guix-devel@gnu.org>
I wonder how scalable this approach is, if many "package maintainers"
each have their own channel for the packages they are maintaining, and
made available this way. I would guess to use this approach the Guix
users have to do "guix package -u --allow-collision"
> Date: Sat, 17 Aug 2024 12:43:11 -0700
> From: Ian Eure <ian@retrospec.tv>
> Whatever the state of Guix proper, you can always find the current
> version of LibreWolf in my personal channel[1], though I don’t
> have a public substitute server, so long build times will await
> you if you choose this route.
next parent reply other threads:[~2024-08-18 0:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5970.1723926982.21382.guix-devel@gnu.org>
2024-08-18 0:11 ` Andy Tai [this message]
2024-08-18 0:48 ` Request for assistance maintaining LibreWolf Ian Eure
2024-08-17 16:44 Ian Eure
2024-08-17 18:00 ` Sergio Pastor Pérez
2024-08-17 19:43 ` Ian Eure
2024-08-18 8:35 ` Christopher Baines
2024-08-18 16:50 ` Ian Eure
2024-08-19 1:53 ` Suhail Singh
2024-08-19 8:53 ` Christopher Baines
2024-08-19 23:14 ` Ian Eure
2024-09-12 1:01 ` Maxim Cournoyer
2024-08-19 17:01 ` Sergio Pastor Pérez
2024-08-18 8:37 ` Attila Lendvai
2024-08-18 9:07 ` Lars-Dominik Braun
2024-08-17 20:36 ` Ian Eure
2024-08-17 23:08 ` Suhail Singh
2024-08-18 4:07 ` Ian Eure
2024-08-18 21:17 ` Tomas Volf
2024-08-21 20:54 ` Ludovic Courtès
2024-08-22 15:00 ` Ian Eure
2024-08-28 20:48 ` Ludovic Courtès
2024-08-28 23:15 ` Ian Eure
2024-08-29 7:30 ` Tobias Geerinckx-Rice
2024-08-22 16:37 ` André Batista
2024-08-28 20:46 ` Ludovic Courtès
2024-08-28 23:16 ` Ian Eure
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=CAJsg1E_rNRKy0R2YuH+vETQz6Lb-9tvjHQg+4KH2vhb0wYvsDQ@mail.gmail.com \
--to=atai@atai.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.