Re: [ptxdist] lndir'ing sysroot-target

[Michael Olbrich <m.olbrich@pengutronix.de>]

On Sun, Nov 06, 2011 at 02:16:56PM +0100, Erwin Rol wrote:
> >But the only difference is 2 images vs. 1, right? That's not quite that
> >simple. We can easily add an option to not include the ipkgs from the base
> >system. However the resulting image needs to be mounted somewhere. To do
> >this right we would need to strip the mount point from the paths when
> >creating the image. Otherwise the prefix when building and running wont
> >match.
> >The question is why do you want 2 images? Unless you add some ugly hacks
> >you probably need to add some stuff to /etc anyway (e.g. init scripts).
> 
> The two images is not only about "two images" it is also a
> organizational boundary.  The OS is created, installed on the
> hardware and than that finished product is handed to someone that
> will develop applications that run on it.  How those applications
> are installed is a solvable detail.

Well, you can get the 'OS' image from the production build, and the ipkgs
for you applications. What else do you need then to pull everything
together?

> >>PS: is there any documentation on how those mentioned feature should
> >>work, cause the "Help" in ptxdist isn't really helpful.
> >
> >Unfortunately not. That would require several pages od documentation and
> >and nobody is really happy with how these features work anyways...
> >The main problem is, that I have yet to find two people that agree on how
> >something like this is supposed to work. And while we could probably
> >implement a lot of these variations, it would create (or rather already is)
> >a configuration nightmare that only a few experts can handle.
> 
> This sounds like an point where ptxdist could/should be improved.
> Ptxdist is in my eyes a bit to monolithic  (source -> magic ->
> images). It would be really nice to be able to hook into certain
> parts, like the image generation, without to much black magic.  I
> really would like to see Ptxdist move forwards (and not just under
> the hood).  But that discussion could become a very large thread I
> guess.

This won't be a short discussion, but a very welcome one. I've talked a lot
about separating the image generation a bit more. But that's not that easy.
In the end running "ptxdist images" to get on final blob must still be
possible.
We're actually working on some separate tool to create the images, that can
be used separately or by ptxdist to create the images. The main problem we
have here is configuration. Defining the images in kconfig is rather
awkward and not really flexible. However, while we think, we now have
something nice to define images, I still need to work out how to integrate
that with ptxdist...
Any comments on what you would like to see there 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