From: Peter Korsgaard <peter@korsgaard.com>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dhcp: fix cross build
Date: Thu, 09 Nov 2023 15:57:14 +0100 [thread overview]
Message-ID: <87il6bnfed.fsf@48ers.dk> (raw)
In-Reply-To: <pan$e4c2e$65ef9aa7$60d9f1ab$55fd2db7@ID-313208.user.individual.net> (Bernd Kuhls's message of "Tue, 03 Oct 2023 13:12:10 +0200")
>>>>> "Bernd" == Bernd Kuhls <bernd@kuhls.net> writes:
> Am Mon, 2 Oct 2023 22:51:44 +0200 schrieb Yann E. MORIN:
>> So your patch looks like it is correct.
>>
>> However, I would challenge it on other grounds: ISC decided to stop
>> maintaing dhcp starting end of 2022, almost a year ago, when they
>> released the last version of dhcp.
>>
>> Should we just drop that package now and be done with it?
> Hi Yann,
> my patch follows Peter's intention:
> "If it is dead upstream and hard to fix then that naturally makes it
> harder to do, but the intention is to fix it."
> http://lists.busybox.net/pipermail/buildroot/2022-April/640709.html
.. Which was a discussion about supporting it during the support period
of Buildroot 2022.02.x, but OK.
Maybe we should consider dropping it for 2024.02.x.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-11-09 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 19:51 [Buildroot] [PATCH 1/1] package/dhcp: fix cross build Bernd Kuhls
2023-10-02 20:51 ` Yann E. MORIN
[not found] ` <20231002205144.GD2957__28552.5928296678$1696279934$gmane$org@scaer>
2023-10-03 11:12 ` Bernd Kuhls
2023-11-09 14:57 ` Peter Korsgaard [this message]
2023-11-04 21:13 ` Thomas Petazzoni via buildroot
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=87il6bnfed.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@uclibc.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 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.