unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Gottfried <gottfried@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: information about new packages in guix available
Date: Sat, 05 Mar 2022 13:28:09 +0000	[thread overview]
Message-ID: <5eKKB-02HVSljMILH8KS2fzsKoEbhRHxoUj0TOkGfBTJnIGH54QAVEa9Jc5Cu38opt6grUtPUSV68242-Q6abfnO_UDNk3cZiFkfVA5dWMU=@protonmail.com> (raw)
In-Reply-To: <6931bca5-beda-8f27-391f-09b751607960@posteo.de>


[-- Attachment #1.1: Type: text/plain, Size: 797 bytes --]

Hi, Gottfried,

On Friday, March 4th, 2022 at 8:44 PM, Gottfried <gottfried@posteo.de> wrote:

> Hi,
> 

> I would like to know when new packages, (I don't mean updates to
> packages), in guix are available.

I was thinking about this too yesterday. I wanted to know which games were added recently.

> Is it the same to new packages in GNU, which I could know through the "info-gnu@gnu.org mailing list or is there a difference between GNU packages and guix packages?

As far as I know info-gnu is for GNU Projects only, while Guix packages libre software and libre cultural works from any project, including GNU.

> It would safe time to be informed and not look sometimes at the guix packages available in https://guix.gnu.org/de/packages/

It would be a nice service to have.

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1815 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]

  parent reply	other threads:[~2022-03-05 13:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 20:44 information about new packages in guix available Gottfried
2022-03-04 21:17 ` Ricardo Wurmus
2022-03-06 16:05   ` Gottfried
2022-03-06 16:43     ` Tobias Geerinckx-Rice
2022-03-05 13:28 ` Luis Felipe [this message]
2022-03-08  6:52 ` Remco

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='5eKKB-02HVSljMILH8KS2fzsKoEbhRHxoUj0TOkGfBTJnIGH54QAVEa9Jc5Cu38opt6grUtPUSV68242-Q6abfnO_UDNk3cZiFkfVA5dWMU=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=gottfried@posteo.de \
    --cc=help-guix@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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).