unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix depends on openldap?
Date: Thu, 19 Nov 2020 17:59:38 +0100	[thread overview]
Message-ID: <CAJ3okZ3tstr6FUHhpeqE69ED-vVLncZSvkOiA-5RwYPhb_9psQ@mail.gmail.com> (raw)
In-Reply-To: <DE7F4735-DD79-4389-87DB-A2DC111AEFF1@lepiller.eu>

Hi,

On Thu, 19 Nov 2020 at 17:46, Julien Lepiller <julien@lepiller.eu> wrote:

> >I am still confused.  Why cmake-minimal needs all the protocols that
> >curl supports?  What I was expecting is that cmake-minimal depends on
> >curl-minimal and that both packages are minimal. :-)
>
> >Because all in all, we end with a chubby Guix; which matters when
> >packing it (Docker or system).
>
> I don't think it matters: no reference is retained from guix to openldap, so it won't be added to the pack or docker image. It's only required at build time.

So each time I run "guix environment guix", I potentially download it.
It is annoying when it is not possible to keep the store (for example,
the storage for the store is small or some CI external automation
build, etc.) or when the substitutes of dependencies are not available
(burn CPU) or when the bandwidth is not cheap, etc.

Maybe "packing it" is not the good terminology, but remove unnecessary
dependencies matters.  IMHO.


All the best,
simon


  reply	other threads:[~2020-11-19 17:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 13:41 guix depends on openldap? zimoun
2020-11-19 13:56 ` Efraim Flashner
2020-11-19 14:18   ` Efraim Flashner
2020-11-19 14:32     ` Efraim Flashner
2020-11-19 15:33       ` zimoun
2020-11-19 16:46         ` Julien Lepiller
2020-11-19 16:59           ` zimoun [this message]
2020-11-19 16:11   ` Danny Milosavljevic

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=CAJ3okZ3tstr6FUHhpeqE69ED-vVLncZSvkOiA-5RwYPhb_9psQ@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.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).