From: Anton Mikanovich <amikan@ilbers.de>
To: Balasubramanian Sundaram <balasubramanian.sundaram@sanmina.com>,
henning.schild@siemens.com
Cc: isar-users@googlegroups.com, jan.kiszka@siemens.com
Subject: Re: [PATCH] image.bbclass: set file timestamps inside the rootfs and initramfs image
Date: Thu, 10 Nov 2022 13:03:20 +0300 [thread overview]
Message-ID: <c98a3fbb-0c52-d7b7-7aad-2db7ad88aed0@ilbers.de> (raw)
In-Reply-To: <CAMxE6Km4X9X1_4U5v5qeXsmDhtYgUs-BAyfZYFmKwo-K-xiXHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
10.11.2022 12:52, 'Balasubramanian Sundaram' via isar-users wrote:
> Hi
>
> I am using ISAR build system can you help me how to create a recipe
> for *Bluez5*
> * in ISAR build system*
> *
> *
> *Thanks & Regrads*
Hello, Balasubramanian.
Current Debian repositories already provide bluez package (v5.55 for
bullseye),
so you can just add it to IMAGE_INSTALL.
If you need to rebuild bluez to make some changes there, SRC_URI =
"apt://bluez"
can be used (see hello.bb as a reference).
P.S. please avoid replying to existing maillist threads with the new
questions
[-- Attachment #2: Type: text/html, Size: 1284 bytes --]
next prev parent reply other threads:[~2022-11-10 10:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 8:25 venkata.pyla
2022-11-07 8:50 ` Moessbauer, Felix
2022-11-09 6:56 ` Venkata.Pyla
2022-11-07 8:53 ` Henning Schild
2022-11-09 9:27 ` Venkata.Pyla
2022-11-10 7:12 ` Henning Schild
2022-11-20 7:53 ` [PATCH] scripts/repro-test.sh: script to test reproducibility of Isar image venkata.pyla
2022-11-22 7:28 ` Anton Mikanovich
2022-11-22 8:49 ` Venkata.Pyla
2022-12-19 14:41 ` [PATCH 0/2] Test for verifiying reproducible images venkata.pyla
2022-12-28 8:40 ` Anton Mikanovich
2023-01-02 6:24 ` [PATCH] repro-build-test.py: Fix date_epoch time contains byte character b'' venkata.pyla
2023-01-11 5:42 ` Uladzimir Bely
2022-12-19 14:41 ` [PATCH 1/2] cibuilder.py: Add source_date_epoch to build configuration venkata.pyla
2022-12-19 14:41 ` [PATCH 2/2] repro-build-test.py: Test to check images are reproducible venkata.pyla
2023-01-07 0:01 ` Henning Schild
2022-11-21 5:16 ` [PATCH] image.bbclass: set file timestamps inside the rootfs and initramfs image Venkata.Pyla
2022-11-10 9:52 ` Balasubramanian Sundaram
2022-11-10 10:03 ` Anton Mikanovich [this message]
2022-11-10 10:17 ` Balasubramanian Sundaram
2022-11-10 10:19 ` Balasubramanian Sundaram
2022-11-10 10:27 ` Anton Mikanovich
2022-11-10 10:51 ` Balasubramanian Sundaram
2022-11-10 16:30 ` Henning Schild
2022-11-10 17:05 ` Henning Schild
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=c98a3fbb-0c52-d7b7-7aad-2db7ad88aed0@ilbers.de \
--to=amikan@ilbers.de \
--cc=balasubramanian.sundaram@sanmina.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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