public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <ch@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Cc: Alexander Smirnov <asmirnov@ilbers.de>
Subject: Re: [PATCH] isar-bootstrap-helper: Purge /var/lib/apt/lists on cleanup
Date: Tue, 04 Sep 2018 10:56:15 +0200	[thread overview]
Message-ID: <7cce46e3f5ec16fbed650a40730c63c3e0127758.camel@denx.de> (raw)
In-Reply-To: <279d3431-fe77-18e9-a748-a0dec0271d57@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

Hi Jan,

On Mon, 2018-09-03 at 12:17 +0200, Jan Kiszka wrote:
> This saves dozens of MB on the target image. The user just needs to
> run
> "apt-get update" to restore it.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> The lowest hanging fruit for tinyfication. Base image on armhf, e.g.,
> is
> now ~100 MB.
> 
> Claudius, to my understanding, this will not break reproducibility as
> --clean is only done on the final target image, not during the build,
> not on the buildchroots.

I don't think so. And if it does then it should be possible to avoid
it.

regards,
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

            PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
                              Keyserver: hkp://pool.sks-keyservers.net

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-09-04  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 10:17 Jan Kiszka
2018-09-04  8:56 ` Claudius Heine [this message]
2018-09-06 20:47 ` 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=7cce46e3f5ec16fbed650a40730c63c3e0127758.camel@denx.de \
    --to=ch@denx.de \
    --cc=asmirnov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@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