public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 1/4] apt: Generate configs for apt
Date: Thu, 5 Oct 2017 13:14:29 +0200	[thread overview]
Message-ID: <9e154cd2-72ee-fc8a-48c9-6ce295209ff0@siemens.com> (raw)
In-Reply-To: <20171005100807.3369-2-asmirnov@ilbers.de>

Hi,

On 10/05/2017 12:08 PM, Alexander Smirnov wrote:
> Generate reprepro configuration files for apt deployment.
> 
> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
> ---
>   meta-isar/conf/layer.conf                            | 10 ++++++++--
>   meta-isar/recipes-core/images/files/distributions.in |  3 +++
>   meta/classes/image.bbclass                           | 17 ++++++++++++++++-
>   3 files changed, 27 insertions(+), 3 deletions(-)
>   create mode 100644 meta-isar/recipes-core/images/files/distributions.in
> 
> diff --git a/meta-isar/conf/layer.conf b/meta-isar/conf/layer.conf
> index 72a103c..0950a34 100644
> --- a/meta-isar/conf/layer.conf
> +++ b/meta-isar/conf/layer.conf
> @@ -1,5 +1,5 @@
>   # This software is a part of ISAR.
> -# Copyright (C) 2015-2016 ilbers GmbH
> +# Copyright (C) 2015-2017 ilbers GmbH
>   
>   # We have a conf and classes directory, add to BBPATH
>   BBPATH .= ":${LAYERDIR}"
> @@ -13,6 +13,12 @@ BBFILE_PRIORITY_isar = "5"
>   
>   # This should only be incremented on significant changes that will
>   # cause compatibility issues with other layers
> -LAYERVERSION_isar = "2"
> +LAYERVERSION_isar = "3"
>   
>   LAYERDIR_isar = "${LAYERDIR}"
> +
> +# Codename of the repository created by the caching class
> +DEBDISTRONAME = "isar"
> +
> +# Path to the Isar apt repository
> +DEPLOY_DIR_APT ?= "${DEPLOY_DIR}/apt"

Thanks!

I would prefer that being handled the same way the DL_DIR and SSTATE_DIR 
is handled. So the same variable naming scheme (maybe APT_CACHE_DIR) and 
similar default paths (maybe "${TOPDIR}/aptcache"). The deploy dir is 
not really the place to do work in.

If you want to have something deployed to the deploy dir then it should 
be done via a recipe. I would suggest something like a 
"do_deploy_repository_deb" task in image recipes. But thats a separate 
patch.

Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  reply	other threads:[~2017-10-05 11:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 10:08 [PATCH 0/4 v5] Isar apt deployment Alexander Smirnov
2017-10-05 10:08 ` [PATCH 1/4] apt: Generate configs for apt Alexander Smirnov
2017-10-05 11:14   ` Claudius Heine [this message]
2017-10-05 11:43     ` Alexander Smirnov
2017-10-05 12:01       ` Claudius Heine
2017-10-05 10:08 ` [PATCH 2/4] apt: Generate Isar reprepro database Alexander Smirnov
2017-10-05 11:43   ` Claudius Heine
2017-10-09 12:04   ` Henning Schild
2017-10-05 10:08 ` [PATCH 3/4] apt: Populate Isar apt Alexander Smirnov
2017-10-05 10:08 ` [PATCH 4/4] apt: Install packages via multistrap Alexander Smirnov
2017-10-19 15:24   ` [PATCH 4/4 v6] " Alexander Smirnov
2017-10-09 12:00 ` [PATCH 0/4 v5] Isar apt deployment Henning Schild
2017-10-12 10:42   ` Claudius Heine
2017-10-18 11:06   ` Alexander Smirnov
2017-10-18 13:44     ` Henning Schild
2017-10-18 17:10       ` Alexander Smirnov
2017-10-18 17:14         ` Alexander Smirnov
2017-10-19 16:16           ` Henning Schild
2017-10-19 19:38             ` Alexander Smirnov
2017-10-19  8:41         ` Henning Schild
2017-10-19  9:54           ` Baurzhan Ismagulov
2017-10-19 13:30             ` Henning Schild
2017-10-19 15:14               ` Alexander Smirnov
2017-11-21 12:43   ` Christian Storm

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=9e154cd2-72ee-fc8a-48c9-6ce295209ff0@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=asmirnov@ilbers.de \
    --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