From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH 1/7] dpkg-raw: Respect file permissions defined by recipe
Date: Tue, 15 Jan 2019 09:19:08 +0100 [thread overview]
Message-ID: <221acaf9-1542-52eb-96fd-9616d25a79dd@siemens.com> (raw)
In-Reply-To: <6c2a13e5-513f-243f-3d82-317a8a9df228@siemens.com>
On 10.01.19 02:19, [ext] Jan Kiszka wrote:
> On 09.01.19 23:37, Baurzhan Ismagulov wrote:
>> On Mon, Jan 07, 2019 at 02:28:47PM +0100, Jan Kiszka wrote:
>>>>> dh_fixperms overwrites the permissions do_install defined carefully.
>>>>> Skip this step to avoid that.
>> ...
>>>>> --- a/meta/classes/dpkg-raw.bbclass
>>>>> +++ b/meta/classes/dpkg-raw.bbclass
>>>>> @@ -56,9 +56,11 @@ EOF
>>>>> deb_create_rules() {
>>>>> cat << EOF > ${S}/debian/rules
>>>>> #!/usr/bin/make -f
>>>>> +
>>>>> +override_dh_fixperms:
>>>>> +
>>>>> %:
>>>>> dh \$@
>>>>> -
>>>>
>>>> I think it is not a good idea to do that in general. While you might
>>>> have found an example where dh_fixperms caused problems, there are
>>>> probably many where it helps. Say people use "cp" to fill ${D} or
>>>> "echo" to fill ${D}/bin/
>>>
>>> I'm open for better suggestions.
>>
>> dh_fixperms -X from a variable / file?
>>
>> override_dh_fixperms in a conditional makefile include, if exists?
>
> Something like this?
>
> diff --git a/meta/classes/dpkg-raw.bbclass b/meta/classes/dpkg-raw.bbclass
> index 10fb1b9..fa584ee 100644
> --- a/meta/classes/dpkg-raw.bbclass
> +++ b/meta/classes/dpkg-raw.bbclass
> @@ -53,11 +53,14 @@ Description: ${DESCRIPTION}
> EOF
> }
>
> +FIXPERM_EXCLUSIONS = "${@' '.join(['-X ' + x for x in d.getVar('PRESERVE_PERMS', False).split()])}"
> +
> deb_create_rules() {
> cat << EOF > ${S}/debian/rules
> #!/usr/bin/make -f
>
> override_dh_fixperms:
> + dh_fixperms ${EXCLUSIONS}
>
> %:
> dh \$@
>
>
> Then the user would have to specify the files to be excluded with full
> paths:
>
> PRESERVE_PERMS = "/root/.ssh"
> PRESERVE_PERMS += "/etc/network/interfaces.d/wifi"
>
>>
>> That said, I think the right way would be to create proper source packages
>> downstream.
>
> Cannot follow that idea yet: What would be the interface?
>
>>
>> FWIW, meta-eid has a PoC for dh_making a package from bitbake, but one could
>> start with manually debianized packages first.
>>
>> With kind regards,
>> Baurzhan.
>>
>
> Jan
>
Ping.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-01-15 8:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 11:34 [PATCH 0/7] Vacation hacks Jan Kiszka
2019-01-02 11:34 ` [PATCH 1/7] dpkg-raw: Respect file permissions defined by recipe Jan Kiszka
2019-01-07 13:20 ` Henning Schild
2019-01-07 13:28 ` Jan Kiszka
2019-01-07 14:19 ` Henning Schild
2019-01-07 14:20 ` Jan Kiszka
2019-01-07 14:26 ` Jan Kiszka
2019-01-07 16:28 ` Henning Schild
2019-01-07 16:54 ` Jan Kiszka
2019-01-07 17:51 ` Henning Schild
2019-01-07 18:56 ` Jan Kiszka
2019-01-09 15:37 ` Baurzhan Ismagulov
2019-01-10 1:19 ` Jan Kiszka
2019-01-15 8:19 ` Jan Kiszka [this message]
2019-01-15 10:10 ` Baurzhan Ismagulov
2019-01-15 10:13 ` Jan Kiszka
2019-01-02 11:34 ` [PATCH 2/7] bootimg-efi-isar: Run grub-mkimage without own config Jan Kiszka
2019-01-07 13:22 ` Henning Schild
2019-01-07 14:02 ` Jan Kiszka
2019-01-02 11:34 ` [PATCH 3/7] bootimg-efi-isar: Retrieve boot disk during runtime Jan Kiszka
2019-01-02 11:34 ` [PATCH 4/7] isar-cfg-localepurge: Also set /etc/default/locale Jan Kiszka
2019-01-02 11:34 ` [PATCH 5/7] Fix LIC_FILES_CHKSUM paths Jan Kiszka
2019-01-02 11:34 ` [PATCH 6/7] Move repo variables to proper conf file Jan Kiszka
2019-01-02 11:34 ` [PATCH 7/7] Move debian distro conf files to meta Jan Kiszka
2019-01-04 13:49 ` [PATCH 8/7] bootimg-efi-isar: Fix serial console setup for grub Jan Kiszka
2019-01-04 13:50 ` [PATCH 9/7] bootimg-efi-isar: Reformat generated grub.cfg Jan Kiszka
2019-01-07 6:06 ` [PATCH 10/7] bitbake.conf: Clean up and enhance OVERRIDES Jan Kiszka
2019-01-07 8:17 ` Claudius Heine
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=221acaf9-1542-52eb-96fd-9616d25a79dd@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
/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