mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
* [ptxdist] ptxdist options help
@ 2011-11-03 22:48 Erwin Rol
  2011-11-07 19:52 ` Bernhard Walle
  0 siblings, 1 reply; 3+ messages in thread
From: Erwin Rol @ 2011-11-03 22:48 UTC (permalink / raw)
  To: ptxdist

Hey All,

could someone explain the idea behind the following ptxdist options ?

     Build Type (development)
[ ] use pre-built production release
[ ] built on top of another platform
[ ] create dev packages
[ ] use dev packages

- Erwin

-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ptxdist] ptxdist options help
  2011-11-03 22:48 [ptxdist] ptxdist options help Erwin Rol
@ 2011-11-07 19:52 ` Bernhard Walle
  2011-11-08 11:21   ` Michael Olbrich
  0 siblings, 1 reply; 3+ messages in thread
From: Bernhard Walle @ 2011-11-07 19:52 UTC (permalink / raw)
  To: ptxdist

Hi,

* Erwin Rol <mailinglists@erwinrol.com> [2011-11-03 23:48]:
> 
> could someone explain the idea behind the following ptxdist options ?
> 
>     Build Type (development)
> [ ] use pre-built production release
> [ ] built on top of another platform

Don't know about that options, but I'm also interested in the second two
options.

Hopefully somebody of the ptxdist gurus (Michael? Jürgen?) can comment
if that's correct and answer my remaining questions:

> [ ] 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?


Regards,
Bernhard

-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ptxdist] ptxdist options help
  2011-11-07 19:52 ` Bernhard Walle
@ 2011-11-08 11:21   ` Michael Olbrich
  0 siblings, 0 replies; 3+ messages in thread
From: Michael Olbrich @ 2011-11-08 11:21 UTC (permalink / raw)
  To: ptxdist

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-11-08 11:21 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-11-03 22:48 [ptxdist] ptxdist options help Erwin Rol
2011-11-07 19:52 ` Bernhard Walle
2011-11-08 11:21   ` Michael Olbrich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox