public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: srinuvasan.a@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH] technical_overview.md: replace DEPLOY_DIR_DEB with isar-apt repo paths
Date: Fri, 22 May 2026 16:30:43 +0200	[thread overview]
Message-ID: <5e120022-f0c4-4db6-959a-54da0cb6ed1f@ilbers.de> (raw)
In-Reply-To: <20260515110655.671907-1-srinuvasan.a@siemens.com>

Applied to next, thanks.

Zhihang

On 5/15/26 13:06, srinuvasan.a via isar-users wrote:
> From: Srinuvasan A <srinuvasan.a@siemens.com>
>
> Presently do_deploy_deb task adds WORKDIR/*.deb to {REPO_ISAR_DIR}/${DISTRO},
> package lookup during target population uses the mounted /isar-apt repo,
> hence remove outdated references to ${DEPLOY_DIR_DEB}, which is
> not used in current Isar sources.
>
> Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
> ---
>   doc/technical_overview.md | 8 +++++---
>   1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/doc/technical_overview.md b/doc/technical_overview.md
> index 82b2ba0f..b7905be0 100644
> --- a/doc/technical_overview.md
> +++ b/doc/technical_overview.md
> @@ -227,8 +227,9 @@ Both consist of the following steps:
>           `dpkg-deb` to construct a Debian package from a folder of files,
>   	without compiling anything
>   
> -6. Task `do_deploy_deb`: install successfully built packages
> -   `${WORKDIR}/*.deb` to deploy directory `${DEPLOY_DIR_DEB}`
> +6. Task `do_deploy_deb`: add successfully built packages
> +   `${WORKDIR}/*.deb` to the isar-apt repository
> +   `${REPO_ISAR_DIR}/${DISTRO}`
>   
>   ## 3.6 Populate Target Filesystem
>   
> @@ -237,7 +238,8 @@ variable. Task `do_populate` performs the following:
>   
>   1. Parse IMAGE_INSTALL variable.
>   
> -2. Find respective packages in `${DEPLOY_DIR_DEB}`.
> +2. Find respective packages in the isar-apt repository
> +   (`${REPO_ISAR_DIR}/${DISTRO}`), mounted as `/isar-apt` in the rootfs.
>   
>   3. Copy them to deb folder in dedicated target filesystem.
>   

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/5e120022-f0c4-4db6-959a-54da0cb6ed1f%40ilbers.de.

      reply	other threads:[~2026-05-22 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 11:06 srinuvasan.a via isar-users
2026-05-22 14:30 ` Zhihang Wei [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=5e120022-f0c4-4db6-959a-54da0cb6ed1f@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=srinuvasan.a@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