all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Reza Alizadeh Majd <r.majd@pantherx.org>
Cc: 38926@debbugs.gnu.org
Subject: bug#38926: pcmanfm-qt unable to open files by double click
Date: Sun, 5 Jan 2020 10:56:55 +0100	[thread overview]
Message-ID: <20200105105655.5dde2d6c@scratchpost.org> (raw)
In-Reply-To: <c2b99788-f966-4364-9bbf-98f8518e4c25@www.fastmail.com>

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

Hi,

thanks for the patch.

Unfortunately, that way is not acceptable.

Long story short, please make it a regular input.  The reasoning is below:

Guix has better modularity than most of the other distributions that exist.

One of the main uses of modularity is isolation.  If one module uses something
internally, another module must not be disturbed by that fact.

If (executable) package Q requires (library) package B@0.0.1 internally and
   (executable) package R requires (library) package B@0.0.2 internally

then it works just fine to install both Q and R into the same profile.

Why?  Because B is not propagated into the profile (usually when B
is an implementation detail of Q and R and not part of their public
interface).

If, on the other hand, B were propagated then the profile would not be able to
build because the two Bs would conflict.

Debian, Gentoo, Redhat etcetc are different in that they basically ONLY have
propagated-inputs and don't have regular inputs.

They don't have the concept of an "internal" dependency.  All their
dependencies are external, changing the interface.

Looking at https://fossies.org/linux/glib/gio/gio-launch-desktop.c ,
gio-launch-desktop is very small and not connected to anything else.
Propagating it, with all the versioning problems that introduces, would be
unwise.

I propose instead to make glib bin a regular input of pcmanfm-qt and then
substitute* the entire path to gio-launch-desktop in it inside a phase
of pcmanfm-qt.

As a rule of thumb, if something that a regular user would have never heard
of ("glib" "bin" ... ???) makes it directly into his profile (by propagation),
it's probably the wrong thing to do.

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

  reply	other threads:[~2020-01-05  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-04 20:24 bug#38926: pcmanfm-qt unable to open files by double click Reza Alizadeh Majd
2020-01-05  9:56 ` Danny Milosavljevic [this message]
2020-01-05 13:52   ` Reza Alizadeh Majd
2020-01-05 22:37     ` Danny Milosavljevic
2020-01-05 22:57       ` Danny Milosavljevic
2020-01-06 10:06         ` Danny Milosavljevic
2020-01-06 16:38         ` Danny Milosavljevic
2020-01-06 16:45           ` Reza Alizadeh Majd
2020-01-06 19:44             ` Danny Milosavljevic
2020-01-07  6:23               ` Reza Alizadeh Majd
2020-01-07  8:03                 ` Reza Alizadeh Majd
2020-01-07 11:19       ` Hartmut Goebel

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=20200105105655.5dde2d6c@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=38926@debbugs.gnu.org \
    --cc=r.majd@pantherx.org \
    /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.