From: Andy Tai <lichengtai@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 59829@debbugs.gnu.org
Subject: [bug#59829] [PATCH core-updates] gnu: wlroots: Add propagated input xcb-util-renderutil
Date: Fri, 6 Jan 2023 23:13:19 -0800 [thread overview]
Message-ID: <CAJsg1E8qC6F7uVf49R1f=oTJvkTJwyLzXWuYmv9fb2M_XGpdgw@mail.gmail.com> (raw)
In-Reply-To: <87y1qfj2v5.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Hi, I thought propagation inputs are for letting dependent packages to be
able to automatically add this input to its dependency list, like, say,
glib as a propagation input for gtk+ as all gtk+ [programs has glib as an
input or dependency. xcb-util-renderutil seems to have a similar role for
wlroots.
If this is not correct, please file a patch to change it, and merge it.
On Fri, Jan 6, 2023 at 4:07 AM zimoun <zimon.toutoune@gmail.com> wrote:
> Hi,
>
> On Sun, 04 Dec 2022 at 22:44, Andy Tai <lichengtai@gmail.com> wrote:
>
> > gnu/packages/wm.scm (wlroots): Add propagated input xcb-util-renderutil
>
> Could you explain why this propagation is required? Because propagation
> should be avoid at first and it should be used when no other option are
> possible, IMHO.
>
>
> Cheers,
> simon
>
--
Andy Tai, atai@atai.org Skype: licheng.tai, Line.me: andy_tai, WeChat:
andytai1010
Year 2023 民國112年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能
[-- Attachment #2: Type: text/html, Size: 1831 bytes --]
next prev parent reply other threads:[~2023-01-07 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 6:44 [bug#59829] [PATCH core-updates] gnu: wlroots: Add propagated input xcb-util-renderutil Andy Tai
2023-01-06 11:53 ` zimoun
2023-01-07 7:13 ` Andy Tai [this message]
2023-01-09 10:20 ` Simon Tournier
2023-01-11 8:18 ` Andy Tai
2023-01-16 15:01 ` Maxim Cournoyer
2023-01-16 21:34 ` Andy Tai
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='CAJsg1E8qC6F7uVf49R1f=oTJvkTJwyLzXWuYmv9fb2M_XGpdgw@mail.gmail.com' \
--to=lichengtai@gmail.com \
--cc=59829@debbugs.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 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.