public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/7] dpkg-raw: Respect file permissions defined by recipe
Date: Tue, 15 Jan 2019 11:10:14 +0100	[thread overview]
Message-ID: <20190115101014.GE12226@yssyq.m.ilbers.de> (raw)
In-Reply-To: <6c2a13e5-513f-243f-3d82-317a8a9df228@siemens.com>

On Thu, Jan 10, 2019 at 09:19:50AM +0800, Jan Kiszka wrote:
> +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}

Yes, this is what I meant.


> > 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?

In that case, interface wouldn't be needed, since every downstream package
would have its own debian/rules with desired dh_ helper command lines.


With kind regards,
Baurzhan.

  parent reply	other threads:[~2019-01-15 10:10 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
2019-01-15 10:10           ` Baurzhan Ismagulov [this message]
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=20190115101014.GE12226@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --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