mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH v2] README: update
Date: Wed, 16 Oct 2019 13:14:12 +0200	[thread overview]
Message-ID: <20191016111412.15179-1-rhi@pengutronix.de> (raw)
In-Reply-To: <20190901210455.2980-1-rhi@pengutronix.de>

Remove the unclear "Necessary Packages" section, when reading this
README, the sources are obviously already available.

Add links to the web documentation, which also contains all relevant
info about directory structure, quickstart, patching, etc. Keep the
overall idea as a very short intro for new users.

Apply copy editing and very small improvements in the "Idea" section.

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 README | 91 +++++++++-------------------------------------------------
 1 file changed, 13 insertions(+), 78 deletions(-)

diff --git a/README b/README
index 33cf90e0bc19..86e111c1754e 100644
--- a/README
+++ b/README
@@ -1,15 +1,6 @@
 PTXdist
 =======
 
-Necessary Packages
-------------------
-
-In order to build ptxdist, you need this archive:
-
-	ptxdist-<version>.tgz
-
-Extract this archive into some build directory.
-
 Installation
 ------------
 
@@ -33,89 +24,33 @@ For developers who want to work with git versions of PTXdist it is only
 necessary to run "./autogen.sh && ./configure && make" and set the PATH
 variable to the bin/ directory inside the PTXdist tree.
 
-
-Quickstart
-----------
-
-Read the "How to become a PTXdist Guru" guide to get an idea how PTXdist works.
-This document can be found here:
-
-http://www.pengutronix.de/software/ptxdist/appnotes/OSELAS.BSP-Pengutronix-Generic-arm-Quickstart.pdf
-
-
 Idea
 ----
 
-PTXdist is a tool which can be used to generate a root tree for all
-kinds of Linux systems. It was written with embedded systems in mind,
-but there is no reason why you can't use it to configure your firewall,
-router or whatever dedicated "device" comes to your mind.
+PTXdist is a build system which can be used to generate a root tree and
+disk images for all kinds of Linux systems. It was written with embedded
+systems in mind, but there is no reason why you can't use it to
+configure your firewall, router or whatever dedicated "device" comes to
+your mind.
 
 The job works like this: you run 'ptxdist menuconfig' and
-"ptxdist platformconfig", configure what you need. Run 'ptxdist go'
-and you'll find a root tree in <you-platform>/root/. Voila.
+'ptxdist platformconfig', configure what you need. Run 'ptxdist images'
+and you'll find a root tree in ./platform-<name>/root/, and disk images
+in ./platform-<name>/images/. Voilà.
 
 All magic necessary to do these things in a cross enviroment are written
 into "recipies", living in rules/*.make, and config menues in
 rules/*.in.
 
+Documentation
+-------------
 
-Directory Layout
-----------------
-
-These files and directories are supposed to be in an empty project
-directory:
-
-configs/		project specific configurations (optional)
-patches/		project specific patches, overwrites the generic
-			ones from PTXdist
-projectroot/		put files here which are to be copied over to
-			the target's root directory, like for example
-			etc files, scripts, ... Note that the copying
-			has to be done explicitly by some project
-			specific rule file.
-ptxconfig		.config file to configure the userland for
-			your project.
-platformconfig		.config file to configure the platform specific
-			part of your project.
-rules/			contains project specific rules
-src -> ...		link to point to your directory containing
-			tarball files for the packets.
-
-Additionally some other directories are being built when you run
-"ptxdist go" or other start other build targets.
-
-<platform>/build-host/	build directory for host tools
-<platform>/build-cross/	build directory for cross tools
-<platform>/build-target/ build directory for target tools
-<platform>/images/	'ptxdist images' creates tarballs and
-			filesystem images in this directory.
-<platform>/sysroot-target/ target related libs and headerfiles are going to
-			this dir
-<platform>/sysroot-cross/ target related tools, but must run on host are
-			going to this dir
-<platform>/sysroot-host/ host related tools are going to this dir
-
-<platform>/root/	root filesystem for the target
-<platform>/state/	state files (show in which state packages
-			currently are during the compilation)
-
-For more details look at the output of 'ptxdist --help' or see the
-PTXdist manual.
+See <https://www.ptxdist.org/doc/> for the full documentation, which
+includes a quickstart guide as well as a reference for users and
+developers.
 
 Bugs
 ----
 
 - search for FIXMEs
 - see TODO
-
-For documentation please refer:
--------------------------------
-
-http://www.pengutronix.de/software/ptxdist/documentation_en.html
-
-For Patch Tagging please refer:
--------------------------------
-
-http://dep.debian.net/deps/dep3/
-
-- 
2.23.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2019-10-16 11:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-01 21:04 [ptxdist] [PATCH] " Roland Hieber
2019-09-02  8:23 ` Michael Tretter
2019-09-02  9:09   ` Michael Olbrich
2019-09-02 11:36     ` Ladislav Michl
2019-10-16 11:13       ` Roland Hieber
2019-10-16 11:14 ` Roland Hieber [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=20191016111412.15179-1-rhi@pengutronix.de \
    --to=rhi@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