all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
	guix-devel@gnu.org
Subject: Re: Packages grow, no longer fit on a 💾
Date: Fri, 20 Jan 2023 11:51:56 +0100	[thread overview]
Message-ID: <87v8l1qy0j.fsf@gmail.com> (raw)
In-Reply-To: <874jsmd31d.fsf@gnu.org>

Hi Ludo,

On jeu., 19 janv. 2023 at 15:14, Ludovic Courtès <ludo@gnu.org> wrote:

> To me, Emacs is still Emacs, with or without libgccjit.  Of course JIT
> is an improvement, I don’t deny that, but what I mean is that I still
> use Emacs for the very same activities.  This is even more true for
> polkit, because I don’t interact directly with it.

Yeah, there is a trade-off for the maintenance between packages that the
most of us want and specialized packages for user’s own needs.

This reminds me past discussions about parameterized packages. ;-)

Well, for instance the scientific package ’gmsh’ is built full featured
– with GUI using ’fltk’.  That’s a feature that requires big
dependencies; when I mainly use it without GUI.

Another example, git-annex is built full featured – able to run the
WebApp for instance.  That’s a feature that requires a increase of 5%;
when I mainly use a very restricted set of Git-Annex features.

Another instance, the closure of Guix increases a lot from 1.2 to 1.4.
Of course the new version provides many improvements, I do not deny
that, but I still use Guix for the very same activities as I am doing
since version 1.2. ;-)

The tacit policy with Guix packages is that the packages are usually by
default “feature maximalist” or specifically named « <foo>-minimal » …

> Right, and reportedly, Alpine-based images for things like Python are
> smaller than what we do.  There’s no cheating here: images are
> self-contained.

…contrary to Alpine where the packages are usually by default “feature
minimalist” or specifically named « <foo>-<with-feature> ».

Consider the package Emacs [1] and give a look at the recipe for the
package named ’emacs’ [2].  Well, this Alpine package ’emacs’ looks like
the Guix package named ’emacs-minimal’, and then Alpine provides these
variants (subpackages):

    emacs-doc
    emacs-gtk3
    emacs-gtk3-nativecomp
    emacs-nox
    emacs-x11
    emacs-x11-nativecomp

1: <https://pkgs.alpinelinux.org/package/edge/community/x86/emacs>
2: <https://git.alpinelinux.org/aports/tree/community/emacs/APKBUILD>

> Maybe a good topic for a sub-group at the Guix Days?  :-)

Yeah for sure. :-) Although, from my point of view, the main issue is
about a policy for package inclusion; I mean there is no secret: light
images means images with less features. :-)

My personal and biased opinion is that Guix should follow minimalist
packages as default packages and provides more variants.  But the
maintenance cost is not free, IMHO. :-)

Cheers,
simon


  reply	other threads:[~2023-01-20 12:17 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 22:07 Packages grow, no longer fit on a 💾 Ludovic Courtès
2023-01-15  5:51 ` kiasoc5
2023-01-15  8:07 ` Liliana Marie Prikler
2023-01-16  2:09   ` Maxim Cournoyer
2023-01-16  5:17     ` Liliana Marie Prikler
2023-01-16 13:27       ` Maxim Cournoyer
2023-01-17 16:15     ` Ludovic Courtès
2023-01-15 12:56 ` Akib Azmain Turja
2023-01-15 17:00 ` pelzflorian (Florian Pelz)
2023-01-17 16:25   ` Ludovic Courtès
2023-01-17 23:05     ` zimoun
2023-01-17 23:49       ` zimoun
2023-01-18 21:04         ` Grandfathering store paths considered harmful (was: Packages grow, no longer fit on a 💾) Liliana Marie Prikler
2023-01-19 14:28           ` Grandfathering store paths considered harmful Ludovic Courtès
2023-01-19 18:10             ` Liliana Marie Prikler
2023-01-19 14:14       ` Packages grow, no longer fit on a 💾 Ludovic Courtès
2023-01-20 10:51         ` Simon Tournier [this message]
2023-01-20 14:54           ` Maxim Cournoyer
2023-01-18  2:41     ` kiasoc5
2023-01-18  8:43       ` indieterminacy
2023-01-19 14:32       ` Ludovic Courtès
2023-01-20 11:06         ` Simon Tournier
2023-01-17  8:06 ` Efraim Flashner
2023-01-17 16:18   ` Ludovic Courtès
2023-01-17 21:54     ` John Kehayias
2023-01-19 15:30       ` Katherine Cox-Buday
2023-01-17 15:06 ` Simon Tournier
2023-01-19 14:34   ` Ludovic Courtès
2023-01-18 20:44 ` Paul Jewell via Development of GNU Guix and the GNU System distribution.
2023-01-19 13:04   ` Joshua Branson
2023-01-19 14:37   ` Ludovic Courtès
2023-01-19 16:12     ` Katherine Cox-Buday
2023-01-19 18:07   ` Akib Azmain Turja
2023-01-20 15:30     ` Csepp
2023-01-20 17:34       ` Akib Azmain Turja
2023-01-21 12:29         ` bokr
2023-01-21 15:55           ` Akib Azmain Turja
2023-01-20 12:11   ` Simon Tournier

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=87v8l1qy0j.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=pelzflorian@pelzflorian.de \
    /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.