On Thu, Mar 5, 2015 at 6:42 PM, Hisham Muhammad <his...@gobolinux.org> wrote:
> On 4 March 2015 at 12:51, Sergio Tortosa Benedito <serto...@gmail.com> > wrote: > > Even though I'm still trying to get up with Gobo's build system, I'm > still > > thinking this must change drastically what we have now it's quite a mess > > (understandable, due to the lack of contributors). > > I think there's a need for a unified tool (name it upstream ALFS, name it > > Bootstrap, name it <insert cool name here>) because if we have a look at > > everything we have right now there's: GoboALFS, BuildLiveCD, LiveCD , > ALFS > > and Bootstrap (though it's not used). > Yes, you are right here. Our tools should definitely be merged into a single package. For instance, GoboALFS and BuildLiveCD could be shipped as a single entity. The same applies to LiveCD and ConfigTools. > > Here we have a very big maintenance problem as trying to follow this > program > > it's pretty though (because it does not only distribute among it's own > > files, but also among others files, and even modifies them). > > I'm sending this e-mail with triple intention: the first I hope someone > > helps me understand how BuildLiveCD fits inside GoboALFS, second to shed > > some light on this problem, third to start a discussion about what > should be > > done (to change, to create or to stay). > > BTW, just in case anyone gets angry with me, I'm not trying to attack > anyone > > just trying to make Gobo more accessible and help with areas which seem > to > > need some love. > > No offense taken. I agree with you, I used to know all this complex > stuff by heart but now if I would try to get it up and running myself > I'd probably spend a lot of time. > > Yes, the build system is overcomplicated. I think it already has been > improved with GoboALFS but I haven't kept up with the details. Lucas > is the one who has the answers right now. > > Sorry for not having better answers and just pinging Lucas again :) > GoboALFS does three things: (1) it prepares the build environment to execute JHALFS (that's the actual name of the third-party package that implements ALFS), used to compile the basic packages from LFS (2) compiles some extra desktop software like Xorg and a window manager using the Compile tool (3) invokes tools from BuildLiveCD to create the squashfs files and the actual ISO As I mentioned above, it would be best to merge GoboALFS and BuildLiveCD somehow (and maybe ditch the Bootstrap tool). I don't care much about the name of the final tool, but there is no question that it should be a unified beast. Hope this helps somehow. Lucas
_______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
