unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: guix depends on openldap?
Date: Thu, 19 Nov 2020 15:56:34 +0200	[thread overview]
Message-ID: <20201119135634.GE2306@E5400> (raw)
In-Reply-To: <CAJ3okZ3ie759vEHfjktMmPJ6VivO1jQyvKuJz0AgKRauruVNtQ@mail.gmail.com>

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

On Thu, Nov 19, 2020 at 02:41:51PM +0100, zimoun wrote:
> Dear,
> 
> This morning I garbage-collected some old items and pulled.  Well, I
> was then  surprised that "guix environment guix" fetches 'openldap'.
> Is it expected?
> 
> --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?

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-11-19 13:57 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 [this message]
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
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=20201119135634.GE2306@E5400 \
    --to=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).