From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Prafulla Giri <pratheblackdiamond@gmail.com>, 43198@debbugs.gnu.org
Subject: [bug#43198] Questions about "Add breeze icon assets"
Date: Mon, 26 Oct 2020 20:07:19 +0100 [thread overview]
Message-ID: <bae9c62d-5411-0d72-e472-5c15f17b960c@crazy-compilers.com> (raw)
In-Reply-To: <CAFw+=j1+2NZqGtOSGsvGKaZgpLe6CcEcCkxa07rZm3oJ8=pKtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
Hi Prafulla,
sorry, I'm late for the show and this is already merged. I packages
quite a lot KDE packages and also made several attempts to make
plasma-desktop run on guix.
I'm curious about breeze-artwork and breeze and have some questions:
1. What is the reason you broke up breeze into breeze-assets and
breeze? What is the use of having a package "breeze-assets"?
I'm asking since in guix we typically do not split up packages this
way, but are using different "outputs".
2. What is the reason you inherit breeze(-artwork) from breeze-icons?
I'm asking since
a) breeze-icons are part of KDE Frameworks, whereas breeze is part
of KDE Plasma. So I expect these to be somewhat independent of each
other, as one can see by quite different version numbers.
b) While breeze-assets inherits breeze-icons, it overwrites all
information inherited from except of the build-system and some
inputs. Even the version is different.
3. What is the reason for breeze becoming unified with breeze-icons?
I'm asking since, as explained above, I'd expect these to be
somewhat independent of each other. (breeze of course requires
breeze-icons).
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 2135 bytes --]
next prev parent reply other threads:[~2020-10-26 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 8:22 [bug#43198] Add breeze icon assets Prafulla Giri
2020-09-04 9:29 ` Ludovic Courtès
[not found] ` <CAFw+=j2GyvfVWw-qsR1ju4+CEVAzhfP7p6hociAfF1YcBDOuSg@mail.gmail.com>
2020-09-04 11:00 ` [bug#43198] Fwd: " Prafulla Giri
2020-09-07 8:06 ` Ludovic Courtès
2020-09-08 11:11 ` Prafulla Giri
2020-09-08 11:25 ` [bug#43198] Fwd: " Prafulla Giri
2020-09-09 7:26 ` bug#43198: " Ludovic Courtès
2020-09-09 8:27 ` [bug#43198] " Prafulla Giri
2020-10-26 19:07 ` Hartmut Goebel [this message]
2020-10-27 4:35 ` [bug#43198] Questions about "Add breeze icon assets" Prafulla Giri
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=bae9c62d-5411-0d72-e472-5c15f17b960c@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=43198@debbugs.gnu.org \
--cc=pratheblackdiamond@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 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.