From: tot-to <gentoo-dev.list@tot-to.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] USE=desktop-file request
Date: Wed, 06 Jan 2016 16:23:39 +0000 [thread overview]
Message-ID: <20160106162338.1e75682e@localhost> (raw)
I'm a user of a KISS wm, which does not provide Windows™-like menus,
desktop icons, etc. GUI software is called just by typing the binary
name in PATH, just like any other software. For me the desktop-files are
some kind of useless junk.
Recently a lot of software were made harddep on
dev-util/desktop-file-utils, i.e. from now on there are not only junk
text files, but also a junk software required without any reason. I've
added it to /etc/portage/profile/package.provided and everything
compiles and works just fine. It means that in reality there is no real
need in this software.
Please make these dependencies optional.
Reproducible: Always
Steps to Reproduce:
1. echo dev-util/desktop-file-utils-0.22
>> /etc/portage/profile/package.provided
2. emerge -C dev-util/desktop-file-utils
3. emerge -1 `equery d dev-util/desktop-file-utils | awk '{print $1}' |
sed s/^/=/g`
Actual Results:
No crashes or any kind of problems
Expected Results:
Build crash due to lack of hard dependency
To be more specific, here is all the software on my system, that
depends on dev-util/desktop-file-utils, but compiles and works just
fine without it: $ equery d dev-util/desktop-file-utils
* These packages depend on dev-util/desktop-file-utils:
app-office/dia-0.97.3 (dev-util/desktop-file-utils)
app-text/evince-2.32.0-r4 (dev-util/desktop-file-utils)
app-text/gnome-doc-utils-0.20.10-r1 (dev-util/desktop-file-utils)
dev-cpp/atkmm-2.24.1 (dev-util/desktop-file-utils)
dev-cpp/cairomm-1.12.0-r1 (dev-util/desktop-file-utils)
dev-cpp/glibmm-2.46.1 (dev-util/desktop-file-utils)
dev-cpp/gtkmm-2.24.4-r3 (dev-util/desktop-file-utils)
dev-cpp/pangomm-2.38.1 (dev-util/desktop-file-utils)
dev-libs/atk-2.18.0 (dev-util/desktop-file-utils)
dev-libs/libIDL-0.8.14 (dev-util/desktop-file-utils)
dev-libs/libcroco-0.6.9 (dev-util/desktop-file-utils)
dev-libs/libsigc++-2.6.2 (dev-util/desktop-file-utils)
dev-python/pygobject-2.28.6-r55 (dev-util/desktop-file-utils)
dev-python/pygtk-2.24.0-r4 (dev-util/desktop-file-utils)
dev-util/gtk-update-icon-cache-3.16.7 (dev-util/desktop-file-utils)
gnome-base/gsettings-desktop-schemas-3.18.1
(dev-util/desktop-file-utils) gnome-base/libglade-2.6.4-r2
(dev-util/desktop-file-utils) gnome-base/librsvg-2.40.11
(dev-util/desktop-file-utils) gnome-extra/libgsf-1.14.34
(dev-util/desktop-file-utils) media-libs/libart_lgpl-2.3.21-r2
(dev-util/desktop-file-utils) sys-block/gparted-0.24.0
(dev-util/desktop-file-utils) x11-libs/gdk-pixbuf-2.32.2
(dev-util/desktop-file-utils) x11-libs/gtk+-2.24.28-r1
(dev-util/desktop-file-utils) x11-libs/pango-1.38.1
(dev-util/desktop-file-utils) x11-themes/gtk-engines-2.20.2-r2
(dev-util/desktop-file-utils)
next reply other threads:[~2016-01-06 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 16:23 tot-to [this message]
2016-01-06 18:59 ` [gentoo-dev] USE=desktop-file request Sergey Popov
2016-01-06 19:47 ` tot-to
2016-01-06 21:29 ` Rich Freeman
2016-01-06 21:59 ` Matthias Maier
2016-01-07 2:42 ` Peter Stuge
2016-01-09 8:24 ` Mart Raudsepp
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=20160106162338.1e75682e@localhost \
--to=gentoo-dev.list@tot-to.com \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox