On 13.05.2012 21:50, Guido Berhoerster wrote:
On 13.05.2012 20:14, Stephan Kulow wrote:
Someone needs to fix them build and then this will be the case. But as the only one who cares for this is me, it only gets very little attention. And with so little interest the live cds get, I consider dropping them alltogether.
That might have to do with the fact that the byzantine build system in openSUSE:Factory:Live is completely undocumented. A couple of weeks ago I started looking into producing an Xfce LiveCD, building a simple non-installable CD with kiwi was rather straightforward, integrating with the openSUSE:Factory:Live packages was not and I gave up in frustration after some time. I'm still interested though and have a bunch of questions queued up, are you the only one who has an understanding of how these LiveCDs are built?
It's not really complicated, I wonder where you failed - and I'm really having a huge IRC time window to not miss me. Anyway. The only thing that's different between a normal kiwi build and openSUSE:Factory:Live is that the package lists change so often with factory. So I have a process that calculates a package list for GNOME and KDE (and the DVDs and addons). That process commits a plain text file in e.g. package-lists-gnome.i586. That creates a package named package-lists-openSUSE-GNOME-cd that will require all those packages. These requires then make up most of the buildrequires of kiwi-image-livecd-gnome.i586. This package will then create a local repo of the buildrequires and then call kiwi. After that happens some preparations for the profiling, but that's not the part that usually fails. But for completness: the package built from kiwi-image-livecd-gnome.i586 is downloaded and run in a kvm to create a clicfs profile. That again is commited into preload-lists-gnome-i586 and the preload list and the original kiwi image will then be profiled in a 3rd package called kiwi-profiled-livecd-gnome.i586. Out of this the final ISO drops. To get it on download.opensuse.org though we need a FTP product, which then again lives in openSUSE:Factory and is generated from _product and is called _product:openSUSE-ftp-livetree-gnome-i586. But that is just a wrapper product to give the resulting ISO the final file name including build number for factory. Leaving out the profiling would this make quite a bit simpler, but I considered a big advantage - and as I said: normally it's not the problem. The problems are *way* more often problems you would get with plain kiwi too. Factory is just moving too fast for kiwi. UsrMerge was the latest example. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org