Hello all, as a long time ptxdist users I ended up with some (weird) ptxdist uses cases, some of wich simply are from before ptxdist offered something similar, some others I am not so sure if they are possible with "plain" ptxdist.
So I thought to ask here to see if others have similar uses cases and how they solved them. To not get a huge mail with 1000 and 1 topics I start with my most important uses case, that is to be able to build separate (squashfs) images and also version (via git) those images. For example I build a rootfs image with things like webkit and Qt5 (both take serious amounts of CPU power and time to build) and version that. From ptxdist point of view that is a normal build. But than I use the sysroot-* dirs inside a second ptxdist projects to build an "appfs". That only has all software written by my client. Those client packages have no ptxdist-DEPS on ptxdist packages like Qt, because we know for sure those packages are already build because we first build the rootfs. This means we end up with two (git versioned) images that will be overlaymounted to give the full/final "root" filesystem on the target. There are several reasons why I started doing this. - Build times, the rootfs doesn't have to be rebuild when client software is changed. - Target software update images are smaller when only client software (appfs) has to be updated (was important in a time with expensive GSM modems, and it is still useful to reduce in field update times) - Reuse, the rootfs kan be reused for different projects. It is a bit like the yocto layer system, just that the (two) layers are build separately and give their own filesystem images. It has some problems (where acceptable at the time); - copying the systemroot-* dirs is a bad hack, and still needs the original systemroot-* dirs because of all the absolute paths in the files. - the host tools (like cmake) are build twice (in rootfs and appfs) which also takes a considerable amount of time. So is there someone that has similar uses cases and if yes how did you solve it? And would it be an interesting feature for upstream ptxdist (not my implementation) ? - Erwin _______________________________________________ ptxdist mailing list [email protected]
