From: Andreas Reichel <andreas.reichel.ext@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>
Cc: Henning Schild <henning.schild@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 2/4] meta-isar-bin: Generate cache repos
Date: Thu, 21 Sep 2017 10:55:37 +0200 [thread overview]
Message-ID: <20170921085535.GA27874@iiotirae> (raw)
In-Reply-To: <69b055e2-e711-8a94-3e1b-0f066566d7d1@ilbers.de>
On Wed, Sep 20, 2017 at 11:26:20AM +0300, Alexander Smirnov wrote:
>
> After build, there will be the following in the cache (example for hello):
>
> $ ls -1 meta-isar-bin/apt/debian-jessie/pool/main/h/hello/
> hello_0.1+g7f35942-1_amd64.deb
> hello_0.1+g7f35942-1_armhf.deb
> hello_0.1+g7f35942-1_i386.deb
>
This looks like a misdesign, because meta-layers should not be populated
by the build process and furthermore, should contain recipes and not a
cache itself. It would be like the sstate-cache lying inside meta-oe...
Why not define a variable like 'DEB_CACHE_DIR' or something alike and
use this directory. Then you also have more flexibility and can handle
multiple different caches, i.e. the caches become selectable and
independent of the layer itself...
Furthermore, you could set the DEB_CACHE_DIR variable in the local.conf
snippents for multiconf and then you can have separate caches for
different target architectures and don't mix everything up in one pool.
This way you can easily drop a pool by architecture without sorting
files out.
Kind regards
Andreas
--
Andreas Reichel
Dipl.-Phys. (Univ.)
Software Consultant
Andreas.Reichel@tngtech.com, +49-174-3180074
TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring
Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller
Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082
next prev parent reply other threads:[~2017-09-21 8:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 12:20 [PATCH v2 0/4] Basic binary cache implementation Alexander Smirnov
2017-09-19 12:20 ` [PATCH v2 1/4] meta-isar-bin: Add reprepro configs Alexander Smirnov
2017-09-20 7:58 ` Henning Schild
2017-09-20 8:12 ` Alexander Smirnov
2017-09-20 8:38 ` Henning Schild
2017-09-20 8:51 ` Alexander Smirnov
2017-09-19 12:20 ` [PATCH v2 2/4] meta-isar-bin: Generate cache repos Alexander Smirnov
2017-09-20 8:11 ` Henning Schild
2017-09-20 8:26 ` Alexander Smirnov
2017-09-21 8:55 ` Andreas Reichel [this message]
2017-09-21 9:21 ` Claudius Heine
2017-09-22 10:56 ` Baurzhan Ismagulov
2017-09-25 10:49 ` Claudius Heine
2017-09-25 11:57 ` Alexander Smirnov
2017-09-25 13:48 ` Claudius Heine
2017-09-19 12:20 ` [PATCH v2 3/4] meta-isar-bin: Populate cache Alexander Smirnov
2017-09-20 8:22 ` Henning Schild
2017-09-20 8:49 ` Alexander Smirnov
2017-09-19 12:20 ` [PATCH v2 4/4] meta-isar-bin: Install packages via multistrap Alexander Smirnov
2017-09-20 8:28 ` 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=20170921085535.GA27874@iiotirae \
--to=andreas.reichel.ext@siemens.com \
--cc=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