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] ptxdist options help
Date: Tue, 8 Nov 2011 12:21:00 +0100	[thread overview]
Message-ID: <20111108112100.GY20768@pengutronix.de> (raw)
In-Reply-To: <20111107195247.GA19701@regiomontanus.bwalle.de>

On Mon, Nov 07, 2011 at 08:52:47PM +0100, Bernhard Walle wrote:
> > [ ] create dev packages
> 
> This option creates (in addition to the ipk packages that can be
> installed on the target and that are used to create the target image)
> for each package a PKGNAME_$HASH_$ARCH-dev.tar.gz  (in
> platform-$PLATFORM/packages) that contains everything the packages
> installs, not only the subset that is selected by the package.mk.
> Especially it contains header files for libraries that are not on the
> target. So some kind of $package.deb + $package-dev.deb.
> 
> This package can be used in this step:
> 
> > [ ] use dev packages
> 
> If a development package is available, then ptxdist uses the contents of
> the development package to package the ipk package and to build the
> sysroot. It doesn't compile the package from source. This even works if
> the source isn't available.
> 
> One remaining question: What exactly is the checksum? Is it honoured in
> the process when ptxdist checks if it uses the development package
> instead of building it from source? The ptxdist sources are a bit hard
> to read in that area ... at least for me. ;) Wouldn't it make sense to
> include the version number of the package in the file name?

The hash ist the md5sum of all selected options for the package, more or
less this:
grep PTXCONF_<PKG>.*= | md5sum

PTXdist looks for: <pkg>-<pkg_version>-<arch>-<hash>-dev.tar.gz

It does not detect any changes to the patches (I tried that, it doesn't
perform well) or the makefile (other than the version), so don't change
anything there that will change the output of the install stage.

You can keep differnt versions of the same package in one pool, but I would
not recommend to put packages of different ptxdist versions in one pool
unless you've carefully reviewed all changes.

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:[~2011-11-08 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 22:48 Erwin Rol
2011-11-07 19:52 ` Bernhard Walle
2011-11-08 11:21   ` 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=20111108112100.GY20768@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