all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>
Cc: help-guix@gnu.org
Subject: Re: Security of packages in official repo
Date: Thu, 26 Nov 2020 20:50:28 +0100	[thread overview]
Message-ID: <868sansxrv.fsf@gmail.com> (raw)
In-Reply-To: <854klcq6ne.fsf@beadling.co.uk>

Hi,

On Thu, 26 Nov 2020 at 19:07, Phil <phil@beadling.co.uk> wrote:

> The important point is that the patch is vetted by the members of
> guix-patches@gnu.org mail list.  And I assume packages which appear
> inappropriate for whatever reason are not accepted by members of this
> list?

Anyone can subscribe to guix-patches and discuss the patches.  Give a
look at:

   <http://issues.guix.gnu.org/>

However, a set of restricted people have commit access and so push code
which is compliant with the GNU standards.


> As a workaround it would seem perfectly possible to host a private Guix
> channel with a subset of packages on that have been internally vetted,
> but it would be more in the spirit of Guix to contribute and use the
> official package repo.

Yes, custom Channels [1] is the way to deliver variants.  Well, it is up
to the channel maintainer to set the rules of the very channel; for
instance, provide or not non-free software.  Therefore, the Wild West
could happen to some custom Channels.

1:  <https://guix.gnu.org/manual/devel/en/guix.html#Channels>


All the best,
simon




      reply	other threads:[~2020-11-26 19:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 12:32 Security of packages in official repo Phil
2020-11-26 16:01 ` zimoun
2020-11-26 16:51   ` Ricardo Wurmus
2020-11-26 19:30     ` zimoun
2020-11-26 21:10       ` Ricardo Wurmus
2020-11-26 21:35         ` zimoun
2020-11-26 19:07   ` Phil
2020-11-26 19:50     ` zimoun [this message]

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=868sansxrv.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=phil@beadling.co.uk \
    /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.