mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] adding md5 list to final image
Date: Wed, 9 Jan 2013 16:53:52 +0100	[thread overview]
Message-ID: <20130109155352.GM13335@pengutronix.de> (raw)
In-Reply-To: <50ED7151.9050203@erwinrol.com>

On Wed, Jan 09, 2013 at 02:32:01PM +0100, Erwin Rol wrote:
> I hacked scripts/lib/ptxd_make_image_prepare_work_dir.sh to add a /.md5
> file to the image that holds all MD5's of all files, so I can verify on
> a running system if everything really is OK.
> 
> Of course ptxdist is a moving target and with every update of ptxdist my
> hack does not apply and I have to tweak it again.

You don't need to copy the whole file. Just redefining
'ptxd_make_image_prepare_work_dir_impl' should be enough.

> What is the correct place to add files to the final image? The thing is
> for something like making that /.md5 file I need access to the final
> image content.
> 
> Anny hints are welcome!

Maybe some post-install script works? I'm not sure when ipkg/opkg calls
those. There is no explicit hook for anything like this in ptxdist, but
patches are welcome :-).

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

      reply	other threads:[~2013-01-09 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 13:32 Erwin Rol
2013-01-09 15:53 ` Michael Olbrich [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=20130109155352.GM13335@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