From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>,
Raphael Pavlidis <raphael.pavlidis@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH/next 02/13] package/dmenu-wayland: new package
Date: Fri, 24 Nov 2023 09:43:05 +0100 [thread overview]
Message-ID: <20231124094305.64c322bd@windsurf> (raw)
In-Reply-To: <CAHDQB6M3-hgq+Pdyz=fS3G=f4xh_OLJXLEmkfKZpi87qQEEqLg@mail.gmail.com>
Hello,
On Thu, 23 Nov 2023 12:13:32 -0700
Adam Duskett <adam.duskett@amarulasolutions.com> wrote:
> Forgot to mention, does it really matter if I use
> ln -sf dmenu-wl $(TARGET_DIR)/usr/bin/dmenu vs what is there now? Does it
> not achieve the same goal?
Well in:
define DMENU_WAYLAND_SYMLINK_DMENU_WL
cd $(TARGET_DIR)/usr/bin && \
ln -sf dmenu-wl dmenu
endef
the indentation was not correct, so I wanted to point this out. But
while writing this, I realized that:
define DMENU_WAYLAND_SYMLINK_DMENU_WL
ln -sf dmenu-wl $(TARGET_DIR)/usr/bin/dmenu
endef
was simpler and cleaner.
I'm not sure how you don't realize that doing directly "ln" is simpler
than cd+ln.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-24 8:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 0:08 [Buildroot] [PATCH 00/13] Sway fixups Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 01/13] package/sway/Config.in: select BR2_PACKAGE_XKEYBOARD_CONFIG Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 02/13] package/dmenu-wayland: new package Adam Duskett
2023-11-23 13:44 ` Thomas Petazzoni via buildroot
2023-11-23 19:12 ` Adam Duskett
2023-11-23 19:13 ` Adam Duskett
2023-11-24 8:43 ` Thomas Petazzoni via buildroot [this message]
2023-11-24 8:41 ` Thomas Petazzoni via buildroot
2023-11-23 0:08 ` [Buildroot] [PATCH/next 03/13] package/tllist: " Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 04/13] package/fcft: " Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 05/13] package/libutempter: " Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 06/13] package/foot: " Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 07/13] package/ncurses: install foot terminfo if foot is selected Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 08/13] package/sway: enable bash-completion support Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 09/13] package/sway: enable default-wallpaper support Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 10/13] package/sway: enable swaybar support Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 11/13] package/sway: enable swaybar tray support Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 12/13] package/sway: enable swaynag support Adam Duskett
2023-11-23 0:08 ` [Buildroot] [PATCH/next 13/13] package/sway/Config.in: Add a help note about the default terminal Adam Duskett
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=20231124094305.64c322bd@windsurf \
--to=buildroot@buildroot.org \
--cc=adam.duskett@amarulasolutions.com \
--cc=eric.le.bihan.dev@free.fr \
--cc=raphael.pavlidis@gmail.com \
--cc=thomas.petazzoni@bootlin.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.
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.