unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret <dev@jpoiret.xyz>
To: Felix Lechner <felix.lechner@lease-up.com>,
	Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: Wilko Meyer <w@wmeyer.eu>,
	guix-devel@gnu.org, Leo Famulari <leo@famulari.name>
Subject: Re: Updates for Go
Date: Tue, 22 Aug 2023 11:59:49 +0200	[thread overview]
Message-ID: <87pm3fv1m2.fsf@jpoiret.xyz> (raw)
In-Reply-To: <CAFHYt55LL6TLDzCrTDKc1hR5Fwb4fT78mJFZz8E3BRN_E66tpQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

Hi Felix,

Felix Lechner via "Development of GNU Guix and the GNU System
distribution." <guix-devel@gnu.org> writes:

> From my experience of packaging Gocryptfs in Debian and here, perhaps
> some reconsideration should be given to the widely unpopular idea of
> using more package functions in Guix. Ending in asterisks, they would
> allow packagers, and perhaps even automated tools, to select exactly
> the particular versions or commits specified for each prerequisite in
> go.mod.

Package functions are really nice, but they don't mesh well with CLI
usage, as well as CI: you'd need to also export a "default" version of
each package for those two to work properly.  Also, while having pinned
versions of dependencies upstream seems like the consensus, I'm not sure
we'd like doing that, be it for the exponential CI work that would be
required.

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

  parent reply	other threads:[~2023-08-22 10:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15 19:57 Updates for Go Katherine Cox-Buday
2023-08-16 17:25 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-17 14:25   ` Katherine Cox-Buday
2023-08-17 21:54     ` Wilko Meyer
2023-08-18  1:52       ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-08-19 11:31       ` Attila Lendvai
2023-08-21 18:14         ` Katherine Cox-Buday
2023-08-21 16:10       ` Katherine Cox-Buday
2023-08-21 17:53         ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-21 18:17           ` Katherine Cox-Buday
2023-08-22  9:59           ` Josselin Poiret [this message]
2023-08-22 13:14             ` Attila Lendvai
2023-08-22 14:24               ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-08-23 16:12                 ` Katherine Cox-Buday
2023-08-27 15:41               ` wolf
2023-08-28 15:18                 ` Katherine Cox-Buday
2023-08-22 11:01         ` Wilko Meyer
2023-08-22 18:06     ` david larsson
2023-08-23 15:35       ` Katherine Cox-Buday
  -- strict thread matches above, loose matches on Subject: below --
2023-08-26  0:29 John Kehayias
2023-08-28 15:14 ` Katherine Cox-Buday

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=87pm3fv1m2.fsf@jpoiret.xyz \
    --to=dev@jpoiret.xyz \
    --cc=cox.katherine.e@gmail.com \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=w@wmeyer.eu \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).