From: Gavin Schenk <g.schenk@eckelmann.de>
To: Michael Olbrich <m.olbrich@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] hostapd: Add systemd service unit
Date: Fri, 25 Oct 2024 13:16:53 +0200 [thread overview]
Message-ID: <8734kko2je.fsf@eckelmann.de> (raw)
In-Reply-To: <Zxt0l7PTShUnF2Gp@pengutronix.de>
Hey Michael,
I really appreciate the effort and time you put into this feedback, thanks.
>> My motivation for the patch was to remove local customization in the BSP.
>> Unfortunately, without the option to rename the configuration, I must continue
>> to to maintain local changes. Does this patch add value or should we discard it?
>
> It's absolutely valuable. In the general case, we can have hostapd running
> with just an kconfig option and a custom config file (and that one is
> always needed anyways).
>
> And I think even your use-case, the customization is simplified:
> You can provide your own projectroot/usr/lib/systemd/system/hostapd.service
> (which changes less often than e.g. hostapd.make) that uses your custom
> hostapd.conf and a "projectroot/etc/hostapd/hostapd.conf -> /dev/null"
> symlink.
> That's much simpler dann a modified hostapd.make or your own rule to
> install the files.
>
> Michael
> PS: I understand why you would like to have a custom path upstream, but the
> reality is, that everybody has a different config file that needs to be
> loaded from a custom location and allowing that in general is a
> maintenance nightmare for upstream PTXdist.
Understand, full ACK!
gsc
prev parent reply other threads:[~2024-10-25 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 5:43 [ptxdist] [PATCH] " Gavin Schenk
2024-09-06 13:59 ` Michael Olbrich
2024-10-08 13:23 ` [ptxdist] [PATCH v2] " Gavin Schenk
2024-10-25 7:32 ` [ptxdist] [APPLIED] " Michael Olbrich
2024-10-25 11:20 ` Artur Wiebe
2024-10-25 14:34 ` Michael Olbrich
2024-10-25 10:36 ` [ptxdist] [PATCH v2] " Michael Olbrich
2024-10-25 11:16 ` Gavin Schenk [this message]
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=8734kko2je.fsf@eckelmann.de \
--to=g.schenk@eckelmann.de \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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