From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to apply a patch for the buildroot makedevs tool
Date: Mon, 26 Apr 2021 23:48:31 +0200 [thread overview]
Message-ID: <87czugemz4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210417071317.GO359705@scaer> (Yann E. MORIN's message of "Sat, 17 Apr 2021 09:13:17 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Ivan, All,
> On 2021-04-16 06:58 +0000, Ivan Castell spake thusly:
>> Hello! I did a patch for the makedevs tool that provides a new 'x' option
>> that allows setting permissions for directories recursively without
>> modifiying permissions for regular files.
> As Peter said, makedev is directly compiled from its single source file
> in Buildroot's tree, so no way to patch it with the standard package
> infrastructure.
With that said, there is no specific reason why this is done like that -
And E.G. mcookie does copy its .c file to the build directory so the
patch step works - So it IMHO makes sense to fix makedevs to also do it
so the normal infrastructure works as expected.
I've sent a series to do that:
https://patchwork.ozlabs.org/project/buildroot/list/?series=240851
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2021-04-26 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 6:58 [Buildroot] Unable to apply a patch for the buildroot makedevs tool Ivan Castell
2021-04-16 22:14 ` Peter Seiderer
2021-04-17 7:13 ` Yann E. MORIN
2021-04-19 5:58 ` Ivan Castell
2021-04-19 17:04 ` Yann E. MORIN
2021-04-26 21:48 ` Peter Korsgaard [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=87czugemz4.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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