From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2014.05.0 released
Date: Mon, 2 Jun 2014 12:42:12 +0200 [thread overview]
Message-ID: <20140602104212.GP26228@pengutronix.de> (raw)
In-Reply-To: <a3d79665b966088d6c8521578c38062f@idefix.lespocky.dyndns.org>
Hi,
On Wed, May 21, 2014 at 04:30:17PM +0200, Alexander Dahl wrote:
> Am 2014-05-12 12:56, schrieb Michael Olbrich:
> > With image rules for UBI and Disk images the 'new' image rules should now
> > cover most basic use-cases.
>
> What's the difference between the old and the new image rules and why
> should one use the one or the other?
First of all, long-term I'd like to remove the old rules. So use the new
rules and yell here if you have a use-case that the new rules cannot
handle.
From a technical perspective, the new rules fix several problems the old
rules have:
- They are 'normal' packages, so they can be overwritten in the BSP.
- They handle dependencies correctly, so they are only rebuilt if needed.
I also tried to make them simpler to use (calculating sectors is a pain).
There is more stuff, and with the image templates you can handle some
really crazy scenarios. Unfortunately most of that is undocumented. So read
the source and ask questions here :-)
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-06-02 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 10:56 Michael Olbrich
2014-05-21 14:30 ` Alexander Dahl
2014-06-02 10:42 ` Michael Olbrich [this message]
2014-06-13 12:54 ` [ptxdist] new image rules (Was: PTXdist 2014.05.0 released) Alexander Dahl
2014-11-25 13:49 ` Alexander Dahl
2014-11-25 14:31 ` Alexander Dahl
2014-11-26 9:54 ` Michael Olbrich
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=20140602104212.GP26228@pengutronix.de \
--to=m.olbrich@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