[Buildroot] [git commit] packages: update sysv S* scripts to 644
Peter Korsgaard
peter at korsgaard.com
Fri Feb 8 13:05:27 UTC 2019
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin at gmail.com> writes:
> Hello,
> On Fri, Feb 8, 2019, 11:39 Peter Korsgaard <peter at korsgaard.com wrote:
>> commit:
>> https://git.buildroot.net/buildroot/commit/?id=590e9e05b683ee521d4984b5cb77a590ebb3fd17
>> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>>
>> Signed-off-by: Matthew Weber <matthew.weber at rockwellcollins.com>
>> Signed-off-by: Peter Korsgaard <peter at korsgaard.com>
>>
> I was not really paying attention when this was discussed. Why does it not
> matter what the permission in the repo is?
It doesn't really, but consistency is nice. We had a big mix of
executable/not executable.
> Where is the executable permission set, if not already in the repo?
During the installation step, E.G.:
define DROPBEAR_INSTALL_INIT_SYSV
$(INSTALL) -D -m 755 package/dropbear/S50dropbear \
$(TARGET_DIR)/etc/init.d/S50dropbear
endef
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list