public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 4/4] meta-isar-bin: Install packages via multistrap
Date: Wed, 4 Oct 2017 13:59:38 +0300	[thread overview]
Message-ID: <fdebcda4-fdfb-f662-8c3c-61115cc7bf5e@ilbers.de> (raw)
In-Reply-To: <20171004110546.266a7a48@md1em3qc>



On 10/04/2017 12:05 PM, Henning Schild wrote:
> Am Mon, 2 Oct 2017 18:45:31 +0300
> schrieb Alexander Smirnov <asmirnov@ilbers.de>:
> 
>> Install custom packages to target image filesystem using multistrap.
>>
>> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
>> ---
>>   meta-isar/recipes-core/images/files/multistrap.conf.in |  9 ++++++++-
>>   meta-isar/recipes-core/images/isar-image-base.bb       |  5 ++++-
>>   meta/classes/ext4-img.bbclass                          |  2 +-
>>   meta/classes/image.bbclass                             | 10
>> ---------- 4 files changed, 13 insertions(+), 13 deletions(-)
>>
>> diff --git a/meta-isar/recipes-core/images/files/multistrap.conf.in
>> b/meta-isar/recipes-core/images/files/multistrap.conf.in index
>> 2d08c36..38d53cf 100644 ---
>> a/meta-isar/recipes-core/images/files/multistrap.conf.in +++
>> b/meta-isar/recipes-core/images/files/multistrap.conf.in @@ -4,7 +4,7
>> @@ [General]
>>   noauth=true
>>   unpack=true
>> -bootstrap=##DISTRO##
>> +bootstrap=##DISTRO## Isar
>>   aptsources=##DISTRO##
>>   configscript=##CONFIG_SCRIPT##
>>   setupscript=##SETUP_SCRIPT##
>> @@ -16,3 +16,10 @@ suite=##DISTRO_SUITE##
>>   components=##DISTRO_COMPONENTS##
>>   packages=##IMAGE_PREINSTALL##
>>   omitdebsrc=true
>> +
>> +[Isar]
>> +packages=##IMAGE_INSTALL##
>> +source=##DEPLOY_DIR_DEB##
>> +suite=##ISAR_DISTRO_SUITE##
>> +components=main
>> +omitdebsrc=true
>> diff --git a/meta-isar/recipes-core/images/isar-image-base.bb
>> b/meta-isar/recipes-core/images/isar-image-base.bb index
>> f4b0125..3b29a53 100644 ---
>> a/meta-isar/recipes-core/images/isar-image-base.bb +++
>> b/meta-isar/recipes-core/images/isar-image-base.bb @@ -46,6 +46,9 @@
>> do_rootfs() { -e
>> 's|##CONFIG_SCRIPT##|./'"$WORKDIR_REL"'/${DISTRO_CONFIG_SCRIPT}|g' \
>> -e 's|##SETUP_SCRIPT##|./'"$WORKDIR_REL"'/setup.sh|g' \ -e
>> 's|##DIR_HOOKS##|./'"$WORKDIR_REL"'/hooks_multistrap|g' \
>> +        -e 's|##IMAGE_INSTALL##|${IMAGE_INSTALL}|g' \
>> +        -e 's|##DEPLOY_DIR_DEB##|copy:///${DEBCACHEDIR}/${DISTRO}|g'
>> \
>> +        -e 's|##ISAR_DISTRO_SUITE##|${DEBDISTRONAME}|g' \
>>              "${WORKDIR}/multistrap.conf.in" >
>> "${WORKDIR}/multistrap.conf"
>>       # Create root filesystem
>> @@ -57,4 +60,4 @@ do_rootfs() {
>>       sudo rm "${IMAGE_ROOTFS}/${DISTRO_CONFIG_SCRIPT}"
>>   }
>>   
>> -addtask rootfs before do_populate after do_unpack
>> +addtask rootfs before do_build after do_populate
>> diff --git a/meta/classes/ext4-img.bbclass
>> b/meta/classes/ext4-img.bbclass index 3e3768b..9fa9aa5 100644
>> --- a/meta/classes/ext4-img.bbclass
>> +++ b/meta/classes/ext4-img.bbclass
>> @@ -34,4 +34,4 @@ do_ext4_image() {
>>       fi
>>   }
>>   
>> -addtask ext4_image before do_build after do_populate
>> +addtask ext4_image before do_build after do_rootfs
>> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
>> index cf819e6..ff8a370 100644
>> --- a/meta/classes/image.bbclass
>> +++ b/meta/classes/image.bbclass
>> @@ -70,16 +70,6 @@ do_populate() {
>>                             includedeb ${DEBDISTRONAME} \
>>                             ${DEPLOY_DIR_DEB}/${p}_*.deb
>>           done
>> -
>> -        sudo mkdir -p ${IMAGE_ROOTFS}/deb
>> -
>> -        for p in ${IMAGE_INSTALL}; do
>> -            sudo cp ${DEPLOY_DIR_DEB}/${p}_*.deb ${IMAGE_ROOTFS}/deb
>> -        done
>> -
>> -        sudo chroot ${IMAGE_ROOTFS} /usr/bin/dpkg -i -R /deb
>> -
>> -        sudo rm -rf ${IMAGE_ROOTFS}/deb
> 
> The comment of what do_populate does is wrong after that.

Thanks for this hint.

> 
>>       fi
>>   }
>>   

  reply	other threads:[~2017-10-04 10:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 15:45 [PATCH v4 0/4] Basic binary cache implementation Alexander Smirnov
2017-10-02 15:45 ` [PATCH 1/4] meta-isar-bin: Add reprepro configs Alexander Smirnov
2017-10-02 15:45 ` [PATCH 2/4] meta-isar-bin: Generate cache repos Alexander Smirnov
2017-10-04  9:03   ` Henning Schild
2017-10-04 10:57     ` Alexander Smirnov
2017-10-04 14:09       ` Henning Schild
2017-10-02 15:45 ` [PATCH 3/4] meta-isar-bin: Populate cache Alexander Smirnov
2017-10-02 15:45 ` [PATCH 4/4] meta-isar-bin: Install packages via multistrap Alexander Smirnov
2017-10-04  9:05   ` Henning Schild
2017-10-04 10:59     ` Alexander Smirnov [this message]
2017-10-04  8:32 ` [PATCH v4 0/4] Basic binary cache implementation Claudius Heine
2017-10-04 11:57   ` Jan Kiszka
2017-10-04 14:29     ` Alexander Smirnov
2017-10-04 15:40       ` Henning Schild
2017-10-04 16:50         ` Alexander Smirnov
2017-10-04 16:58           ` Henning Schild
2017-10-04 17:34       ` Claudius Heine
2017-10-04 18:47         ` Alexander Smirnov
2017-10-05  8:38           ` 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=fdebcda4-fdfb-f662-8c3c-61115cc7bf5e@ilbers.de \
    --to=asmirnov@ilbers.de \
    --cc=henning.schild@siemens.com \
    --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