Hi Dirk,
> I plan to plan helping for half a year now, but the basic requirements are > missing. Since we have our raspberries there was no time, when an initial > boot image and the the obs service repositories could be used together. plan to plan helping is not helping. Thanks for stepping up as a maintainer of the RaspberryPi port, I've approved your request a few days ago. Getting to a state where you can actually build a ARMv6 based image is ongoing work done by me (and others) for 4 months already, but given that there are many fronts to fight on (various armv7 breakages and AArch64 also being a pita sometimes), there is only that much you can do when you're working on something alone. Note that building an image is only perhaps 50% of the work, getting a repository with enough (and current) packages to build an image from is at least half of the other work, and that work is ongoing, a tedious, timeconsuming and often very frustrating job because packages get sometimes broken to build quicker than it took you to fix them to get to build again in the first place. > I do a lot for openSUSE for many years now, but I have no time to learn a > completely new topic how to create a installation system from scratch. So if > we can get a state, where an installation medium is available which matches > current OBS, then I'll help to port some of the stuff and fix problems. Thats when all the work would be done. without additional helping hands to get there, we have little chance to succeed. > the OBS build stuff actually should be exported to the download directories. > Currently all the stuff available for download has nothing to do with the > stuff in the build setup. Everything is totally mangled. Well, it is hidden behind (sometimes not really well documented) APIs or AHIs (Application Human interfaces). In many cases one has to ask somebody who wrote the code on what is going on. Thats just how it is, unfortunately. > I requested maintainer role for devel:ARM:12.3:Contrib:RaspberryPi already, > so that I at least can fix some of the obvious errors like broken links in > the build environment. the 12.3:Contrib project turned out to be a dead end, since it was armv5 and the miscompilations there were just too much effort to get fixed in a stable code tree. Thats why we decided a few weeks ago to focus on ARMv6 and Factory only, where things look a lot more promising. Greetings, Dirk -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
