Re: [Cucumber-linux-development] New Buildscript Format

[Maarten H. <maa...@ao...>]

Hi there, I read through Laura's reply.
Could you show me a few example buildscripts or usecases?
I suggested to build a LFS ch5-like tools-chroot-tarball to use as a way to build the next cucumber.
As long as the package format is compatible with pkgtools, things can evolve later on in the build process.

My own package manager experience is with pkgutils, pacman, and cruxports4slack (https://connochaetos.org/cruxports4slack.html) among others.
cruxports4slack adds the possibility to use Pkgfiles and even PKGBUILD-scripts as a second option next to pkgtools.

Adding pkgtools to LFS is very easy and can be done at the end of ch5 so each package in ch6 is done with the package manager.
That is also how I would create a scripted automated way to build and bootstrap cucumber 2.0.
Adding pacman involves more because it has more features. Pkgutils needs only libarchive and some small hacks.

The splitting up of the buildscript like Scott suggested and demonstrated is at least very readable. 
There is need for a better system/buildscript. 

Hi to all!
Maarten