all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Sarthak Shah <shahsarthakw@gmail.com>, Guix Devel <guix-devel@gnu.org>
Cc: "Gábor Boskovits" <gboskovits@gmail.com>,
	"Pjotr Prins" <pjotr.public12@thebird.nl>,
	"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Discussion on Parameterized Packages
Date: Mon, 15 May 2023 13:49:32 +0200	[thread overview]
Message-ID: <87sfbxzuer.fsf@gmail.com> (raw)
In-Reply-To: <CADBZEV=FjZVCAQx=4MYT-+iKYG+1ZV-AB8gEUHQjiyHj+pd_Ag@mail.gmail.com>

Hi,

On jeu., 11 mai 2023 at 20:38, Sarthak Shah <shahsarthakw@gmail.com> wrote:

> https://blog.lispy.tech/2023/05/parameterized-packages.html
>
> I would really appreciate feedback on
> (1) parameters you'd like to see in Guix
> (2) the user interface for searching/installing/packaging with
> parameters

Just a quick remark.  You are proposing something like:

--8<---------------cut here---------------start------------->8---
 1  (define-public emacs  
 2    (package  
 3      (parameters (and  
 4        (optional jit^ png^ alsa^)  
 5        (one-of motif gtk^ x11!*)))  
 6      (parameter-transforms  
 7        ((x11!)  
 8         (changes-to-be-made-to-the-package)))))  
--8<---------------cut here---------------end--------------->8---

or other variants.  Well, I am a bit afraid by the maintenance of such
packages.  The combinatorial complexity will be exploding and it will be
harder to update such packages, IMHO.

Instead, I would go with something similar as ’package/inherit’.  For
instance, something like that:

--8<---------------cut here---------------start------------->8---
(define-public emacs-params
  (package/parametrized emacs
    (parameters (and
                 (optional jit^ png^ alsa^)
                 (one-of motif gtk^ x11!*)))
    (parameter-transforms
     ((x11!)
      (changes-to-be-made-to-the-package)))))
--8<---------------cut here---------------end--------------->8---

Well, from my point of view, these parametrized packages could go to
specific modules (or channels).  And keeping them separate would avoid
nightmares about maintenance – it is already enough complex without
parameters. :-)

Cheers,
simon


      parent reply	other threads:[~2023-05-15 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 15:08 Discussion on Parameterized Packages Sarthak Shah
2023-05-11 18:04 ` Csepp
2023-05-13 16:54 ` Liliana Marie Prikler
2023-05-13 18:26 ` david larsson
2023-05-13 18:32   ` david larsson
2023-05-15 11:49 ` Simon Tournier [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=87sfbxzuer.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=gboskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    --cc=shahsarthakw@gmail.com \
    /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.