all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: 37940@debbugs.gnu.org
Subject: bug#37940: endless "try upgrading both" cycles
Date: Thu, 31 Oct 2019 10:28:25 +0100	[thread overview]
Message-ID: <20191031102825.46a1c51e@scratchpost.org> (raw)
In-Reply-To: <87a79l7n2z.fsf@web.de>

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

Hi,

On Mon, 28 Oct 2019 01:03:48 +0100
Arne Babenhauserheide <arne_bab@web.de> wrote:

> > Now, it doesn’t sound right that ‘util-linux’ is propagated from glib
> > and from poppler…?  
> 
> Poppler needs glib at runtime and glib needs tools from util-linux at
> runtime?

That doesn't mean glib has to propagate the thing into the profile.

Quite the opposite, Guix is one of the few projects which rightly make the
distinction whether some dependency is an internal implementation detail of
a package or whether it's required in the public interface.

With glib's goal of abstracting stuff from UNIX away I seriously doubt they
intend util-*linux*, of all things, to be part of their public interface.

But you are right that Guix's glib propagates util-linux.  That is most likely
a bug, or it's because of pkg-config files (which also could be solved another
way).

Checking glib-2.50.3, none of their pkg-config files (.pc) mention libmount,
so not sure what's going on.

glib-2.60.6 uses meson which apparently doesn't use pkg-config (?).

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-10-31  9:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-27  9:54 bug#37940: endless "try upgrading both" cycles Arne Babenhauserheide
2019-10-27 17:37 ` Mark H Weaver
2019-10-27 22:46   ` Ludovic Courtès
2019-10-28  0:03     ` Arne Babenhauserheide
2019-10-31  9:28       ` Danny Milosavljevic [this message]
2019-10-30 11:20     ` Diego Nicola Barbato

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=20191031102825.46a1c51e@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=37940@debbugs.gnu.org \
    --cc=arne_bab@web.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.