public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Jan Kiszka" <jan.kiszka@siemens.com>
Cc: "Maxim Yu. Osipov" <mosipov@ilbers.de>, <isar-users@googlegroups.com>
Subject: Re: [PATCH v2] classes/isar-image: Replace the apt sources file with the original
Date: Wed, 19 Dec 2018 10:30:07 +0100	[thread overview]
Message-ID: <20181219103007.62cf5cc4@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <2facc13b-a280-06f6-4d34-982a31868e27@siemens.com>

Am Wed, 19 Dec 2018 08:27:02 +0100
schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:

> On 18.12.18 18:03, Maxim Yu. Osipov wrote:
> > At the final stage of image generation replace the local apt sources
> > file used for bootstrapping with the original APT sources list
> > defined via DISTRO_APT_SOURCES variable.
> > 
> > Signed-off-by: Maxim Yu. Osipov <mosipov@ilbers.de>
> > ---
> >   meta/classes/isar-image.bbclass | 6 ++++++
> >   1 file changed, 6 insertions(+)
> > 
> > diff --git a/meta/classes/isar-image.bbclass
> > b/meta/classes/isar-image.bbclass index 81738ff..4992800 100644
> > --- a/meta/classes/isar-image.bbclass
> > +++ b/meta/classes/isar-image.bbclass
> > @@ -66,7 +66,13 @@ isar_image_cleanup() {
> >       if [ "${ISAR_USE_CACHED_BASE_REPO}" = "1" ]; then
> >           sudo umount -l ${IMAGE_ROOTFS}/base-apt
> >           sudo rmdir ${IMAGE_ROOTFS}/base-apt
> > +        # Replace the local apt we bootstrapped with the
> > +        # APT sources initially defined in DISTRO_APT_SOURCES
> > +        sudo rm -f
> > "${IMAGE_ROOTFS}/etc/apt/sources.list.d/base-apt.list"
> > +        sudo mv "${IMAGE_ROOTFS}/etc/apt/sources-list" \
> > +
> > "${IMAGE_ROOTFS}/etc/apt/sources.list.d/bootstrap.list" fi
> > +    sudo rm -f "${IMAGE_ROOTFS}/etc/apt/sources-list"  
> 
> As I'm counting 3 further sudos here, and actually every other
> command in isar_image_cleanup has that prefix as well: Why not just do
> 
> sudo sh -c ' \
>      cmd1
>      cmd2
>      ...
>      '
> 
> like elsewhere?
> 
> This case would actually need
> 
> sudo isar_image_cleanup() {
>      ...
> }
> 
> if bitbake had that.

prefuncs/postfuncs

As soon as sudo is involved cleandirs will not work anymore, which
should probably be the default way to go.

Henning

> Jan
> 
> >   }
> >   
> >   do_rootfs() {
> >   
> 


  reply	other threads:[~2018-12-19  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-18 17:03 Maxim Yu. Osipov
2018-12-19  7:27 ` Jan Kiszka
2018-12-19  9:30   ` Henning Schild [this message]
2018-12-19 11:45 ` Maxim Yu. Osipov

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=20181219103007.62cf5cc4@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mosipov@ilbers.de \
    /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