all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alexandros Theodotou <alex@zrythm.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 38570@debbugs.gnu.org
Subject: [bug#38570] [PATCH 1/2] gnu: Add gx-plugins-lv2.
Date: Tue, 25 Feb 2020 15:35:37 +0000	[thread overview]
Message-ID: <fba1d20edcd072ec4e2060cf749dfc117acf069f.camel@zrythm.org> (raw)
In-Reply-To: <8fc2300eb10593b64c07975c10a553da9926ad88.camel@zrythm.org>

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

Hi Ricardo,

I apologize for my tone in the last message, it sounded like I was
yelling at you. Would you still prefer to package these separately? It
would need 43 new packages which isn't very efficient or worth the
effort in my opinion considering that they are mostly very
small/minimal plugins.

Also, it would be great if you could have a look at this meta-package
patch for installing all available lv2-plugins: 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38571 .

Thanks,
Alex

On Thu, 2019-12-12 at 10:13 +0000, Alexandros Theodotou wrote:
> Hi Ricardo,
> 
> Thanks for taking a look at this.
> 
> On Thu, 2019-12-12 at 10:11 +0100, Ricardo Wurmus wrote:
> > I think it’s better to err on the side of granularity here and
> > provide
> > the lv2 plugins as individual packages.
> > 
> > We could have a meta package that simply propagates all of the
> > individual packages.
> 
> I think this is a very bad idea in this case, considering:
> a) No one will ever want to install specific gxplugins. Usually
> people
> want to install the "gxplugin suite" - or even all available LV2
> plugins
> b) There are !!!!!!43!!!!!! plugins here. Do you realize how painful
> and unnecessary it would be to add and maintain these packages?
> Especially considering the following point
> c) The total installed file size for all of these is only 7mb
> d) These are all from the same person, who explicitly provides a
> meta-
> repository for packagers so it makes sense to offer them in the same
> package
> 
> If you insist though, I would likely just use my own channel for this
> as I don't want to go through the trouble of adding 40 extra
> packages,
> each only a few KB in size.
> 
> Thanks,
> Alex

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2020-02-25 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12  1:14 [bug#38570] [PATCH 1/2] gnu: Add gx-plugins-lv2 Alexandros Theodotou
2019-12-12  9:11 ` Ricardo Wurmus
2019-12-12 10:13   ` Alexandros Theodotou
2020-02-25 15:35     ` Alexandros Theodotou [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=fba1d20edcd072ec4e2060cf749dfc117acf069f.camel@zrythm.org \
    --to=alex@zrythm.org \
    --cc=38570@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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.