From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH] linux-custom: repack linux-libc-dev
Date: Thu, 13 Jun 2019 18:05:22 +0200 [thread overview]
Message-ID: <20190613160522.GO3977@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20190613101030.156ab5ac@md1za8fc.ad001.siemens.net>
On Thu, Jun 13, 2019 at 10:10:30AM +0200, Henning Schild wrote:
> To me that sounds like an upstream bug that should not just get covered
> up by repacking. I would propose looking into a kernel patch for the
> "debpkg" step. That patch could be carried in your layer(s) and Isar
> while it is pending upstream.
>
> Looking at both ubuntu and debian, old and new .. it should never
> be /usr/include/asm/.
/usr/include/asm is specified in FHS [1]. Debian moves stuff around to support
e.g. installing of cross-dependencies (multiarch [2]). Back when multiarch was
introduced, Debian was alone with that approach; I haven't used other distros
lately, but I haven't heard about others adopting it, either.
That is why I usually use custom kernel packaging in downstream projects. It
arguably ends up simpler than using deb-pkg. But that's a matter of preference.
Given that deb-pkg is Debian-specific, one may ask upstream about that. That
said, Isar aims at providing a working image. And we already repack stuff. I
think the improvement is useful for more than one project, so if there are no
other disadvantages (building for other arches, etc.), I'd be in favor of
merging it.
1. https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf.
2. https://wiki.debian.org/Multiarch/HOWTO
With kind regards,
Baurzhan.
prev parent reply other threads:[~2019-06-13 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 20:10 Cedric Hombourger
2019-06-13 8:10 ` Henning Schild
2019-06-13 8:32 ` Hombourger, Cedric
2019-06-13 15:37 ` Henning Schild
2019-06-13 16:09 ` Henning Schild
2019-06-13 16:05 ` Baurzhan Ismagulov [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=20190613160522.GO3977@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