[Buildroot] [PATCH 1/1] package/genext2fs: bump to version 1.5.0

Arnout Vandecappelle arnout at mind.be
Fri Apr 16 07:33:15 UTC 2021



On 16/04/2021 00:32, stsp wrote:
> 15.04.2021 22:20, Arnout Vandecappelle пишет:
>> On 14/04/2021 23:44, Fabrice Fontaine wrote:
>>> - Retrieve latest version from github
>>> - Drop patch (already in version)
>>>
>>> Fixes:
>>>   - https://bugs.buildroot.org/show_bug.cgi?id=13741
>>>
>>> Signed-off-by: Fabrice Fontaine <fontaine.fabrice at gmail.com>
>>
>>   Applied to master, thanks.
>>
>>   I guess for stable, the patch [1] should be backported rather than bumping. But
>> is it worth spending effort on that for a borderline package like genext2fs?
> I tried really hard (before
> reporting the above bug)
> to find the equivalent
> functionality in mkfs.ext[24],
> and I think its simply not there.
> I think only genext2fs allows
> to set the perms for the root
> node, so I am not sure why it
> is borderline.

 Because on the target, you can generally simply do an mkfs directly of the
partition, then mount it, then set permissions and/or populate it as needed.
Even the mkfs from busybox is usually sufficient on target.

 Of course, Buildroot lives for borderline cases :-). But specifically for the
stable branches, I don't think it's very cost-effective to spend time on making
them work, unless there's a user who does the effort (because they actually need
it).

 Regards,
 Arnout

> Are there any alternatives?
> Buildroot currently creates
> only the rootfs image, and
> for that the default root node
> perms are fine. But once you
> want to create the user partition,
> I think genext2fs is the only
> solution.
> Please let me know if this is
> wrong.


More information about the buildroot mailing list