From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, zimoun <zimon.toutoune@gmail.com>,
Efraim Flashner <efraim@flashner.co.il>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix depends on openldap?
Date: Thu, 19 Nov 2020 11:46:05 -0500 [thread overview]
Message-ID: <DE7F4735-DD79-4389-87DB-A2DC111AEFF1@lepiller.eu> (raw)
In-Reply-To: <CAJ3okZ2X4XV=4ASz0Hjdv-n0gS10YA0WWf5H7HiOYZ9y=6KOtw@mail.gmail.com>
Le 19 novembre 2020 10:33:10 GMT-05:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Hi,
>
>On Thu, 19 Nov 2020 at 15:32, Efraim Flashner <efraim@flashner.co.il>
>wrote:
>
>> > > > --8<---------------cut
>here---------------start------------->8---
>> > > > $ guix graph -t bag --path guix openldap
>> > > > guix@1.1.0-29.4e3ed9b
>> > > > guile-ssh@0.13.1
>> > > > libssh@0.9.5
>> > > > cmake-minimal@3.16.5
>> > > > curl@7.69.1
>> > > > openldap@2.4.49
>> > > > --8<---------------cut
>here---------------end--------------->8---
>> > > >
>> > > > Why does curl need an "Implementation of the Lightweight
>Directory
>> > > > Access Protocol"?
>> > >
>> > > I think a better question is can cmake-minimal depend on a new
>> > > curl-minimal, or does it even need curl at all?
>> >
>> > Looks like I was wrong, there is a curl-minimal afterall
>> >
>> > guix size cmake-bootstrap 199.1 MiB
>> > guix size cmake-minimal
>> > with curl-minimal 198.7 MiB
>> > guix size cmake-minimal 214.9 MiB
>>
>> HOWEVER, anything else that also depends on curl could depend on curl
>> and on curl-minimal, which would be worse than what we have now. So
>I'd
>> leave cmake-minimal with curl and remove the extra bits outlined
>below.
>
>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.
>
>All the best,
>simon
next prev parent reply other threads:[~2020-11-19 16:50 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 [this message]
2020-11-19 16:59 ` zimoun
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=DE7F4735-DD79-4389-87DB-A2DC111AEFF1@lepiller.eu \
--to=julien@lepiller.eu \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@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 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).