mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
Subject: [ptxdist] [PATCH v2 6/6] doc: pre-built packages: some additions
Date: Wed, 13 Sep 2017 17:01:51 +0200	[thread overview]
Message-ID: <20170913150151.1592-7-u.oelmann@pengutronix.de> (raw)
In-Reply-To: <20170913150151.1592-1-u.oelmann@pengutronix.de>

Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
---
 doc/daily_work.inc | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/doc/daily_work.inc b/doc/daily_work.inc
index 2fb27dad1387..431f0666e067 100644
--- a/doc/daily_work.inc
+++ b/doc/daily_work.inc
@@ -680,12 +680,18 @@ Please be careful when using the pre-built archives if you:
 -  intend to use one pre-built archive pool from different PTXdist
    projects.
 
+-  change a global PTXdist configuration parameter (e.g. PTXCONF_GLOBAL_IPV6).
+
 To consider all these precautions the generated pre-built archives are
 not transferred automatically to where the next build expects them. This
 must be done manually by the user of the PTXdist project. Doing so, we
 can decide on a package by package basis if its pre-built archive should
 be used or not.
 
+If you are unsure if your modifications rendered some or all of your pre-built
+archives invalid you can always delete and build them again to be on the safe
+side.
+
 Packages without Pre-Built Archives Support
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -753,6 +759,8 @@ Some major possible use cases are covered in this section:
 -  share pre-built archives between two platforms based on the same
    architecture.
 
+-  increase reproducibility of binaries.
+
 To simply speed up a re-build of the whole project (without development
 on any of the used packages) we just can copy all ``*-dev.tar.gz``
 archives after the first build to the location where PTXdist expects
-- 
2.11.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2017-09-13 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 15:01 [ptxdist] [PATCH v2 0/6] doc: pre-built packages: review chapter 'Using Pre-Built Archives' Ulrich Ölmann
2017-09-13 15:01 ` [ptxdist] [PATCH v2 1/6] doc: pre-built packages: fix typos Ulrich Ölmann
2017-09-13 15:01 ` [ptxdist] [PATCH v2 2/6] doc: pre-built packages: adjust capitalization in headings Ulrich Ölmann
2017-09-13 15:01 ` [ptxdist] [PATCH v2 3/6] doc: pre-built packages: use consistent style in enumerations Ulrich Ölmann
2017-09-13 15:01 ` [ptxdist] [PATCH v2 4/6] doc: pre-built packages: english genitive uses an apostrophe Ulrich Ölmann
2017-09-13 15:01 ` [ptxdist] [PATCH v2 5/6] doc: pre-built packages: enhance phrasing Ulrich Ölmann
2017-09-13 15:01 ` Ulrich Ölmann [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=20170913150151.1592-7-u.oelmann@pengutronix.de \
    --to=u.oelmann@pengutronix.de \
    --cc=ptxdist@pengutronix.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