DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [DistroKit] [PATCH 2/2] doc: intro: update updating instructions
Date: Thu,  8 Aug 2024 14:58:24 +0200	[thread overview]
Message-ID: <20240808125824.2079957-2-rhi@pengutronix.de> (raw)
In-Reply-To: <20240808125824.2079957-1-rhi@pengutronix.de>

For a version update, the versioned PTXdist binary needs to be called
explicitly, otherwise just calling 'ptxdist' will use the PTXdist
version from the current ptxconfig, which will be a no-op.

Explain the purpose of scripts/p-all independently of updating.

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 doc/intro.rst | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/doc/intro.rst b/doc/intro.rst
index d91cc20508c3..498d7160444c 100644
--- a/doc/intro.rst
+++ b/doc/intro.rst
@@ -122,10 +122,15 @@ Maintenance scripts
 Before sending your patch, you should run ``ptxdist lint`` and check its output.
 Your patch should not add any new lint errors.
 
-For migrating PTXdist to a new version, there is the wrapper script
-``scripts/p-all`` that runs PTXdist with the supplied arguments on all existing
-platforms in DistroKit, for example::
+The wrapper script ``scripts/p-all`` runs PTXdist with the supplied arguments on
+all existing platforms in DistroKit.
 
+To migrate DistroKit to a new PTXdist version, first update the *ptxconfig* by
+calling the new PTXdist version explicitely, then use ``scripts/p-all`` (which
+will use the PTXdist version from the updated ptxconfig) to update all
+*platformconfigs:*:
+
+   $ ptxdist-2024.08.0 migrate
    $ ./scripts/p-all migrate
 
 Some platforms use config diffs for kernel and/or barebox packages.
-- 
2.39.2




  reply	other threads:[~2024-08-08 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 12:58 [DistroKit] [PATCH 1/2] scripts: remove update-diffs scripts Roland Hieber
2024-08-08 12:58 ` Roland Hieber [this message]
2024-08-14  7:27 ` Robert Schwebel

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=20240808125824.2079957-2-rhi@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=distrokit@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