tag:blogger.com,1999:blog-2795663664308299225.post6427351194250270410..comments2023-11-05T02:28:20.346-08:00Comments on KDE: Yocto: mature or not?Laszlo Papphttp://www.blogger.com/profile/06121113102679268802noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-2795663664308299225.post-24979162032309926132013-11-17T15:42:00.893-08:002013-11-17T15:42:00.893-08:00Hmm, the situation has changed a lot lately. I wou...Hmm, the situation has changed a lot lately. I would like to express my gratitude to Scott about that. He has made an excellent job on that front!Laszlo Papphttps://www.blogger.com/profile/06121113102679268802noreply@blogger.comtag:blogger.com,1999:blog-2795663664308299225.post-53172396604852556462013-09-04T11:14:17.136-07:002013-09-04T11:14:17.136-07:00> If you're not comfortable contributing fi...> If you're not comfortable contributing fixes upstream, you shouldn't even be *using* Arch, much less developing it.<br /><br />I reported 30-50 bugreports by now. Accordingly, not sure what you mean by "being uncomfortable with contribution". I even had several patches by now.<br /><br />It is not about "being uncomfortable with contribution". It is just that Arch is a widely used distribution. You may probably already know that if you use Arch as you claim.<br /><br />Actually, Dylan builds just fine on Arch, thanks to a few contributors. The only thing you need to do is to backport a couple of patches.<br /><br />debootstrap is pretty tricky to be used due to their shared memory processing with python. I created a bugreport for that. It is not as simple as it seems. I would suggest "systemd-nspawn" in the future which will resolve the issues for you transparently.<br /><br />I do not think that a developer needs to verify any simple changes on many distributions. That is what CIs and their reports are for.<br /><br />Sure, it is Yocto's "fault" as you write. I would rather say trade or decision that they do not support Arch properly.<br /><br />As for 1-2) that you are mentioning here, they were fixed quite a while ago by Arch people. I am not sure what you mean by they are not arch related. I mean, why would you like to prove that? It is obvious. However, Arch is a bleeding edge distribution, and such issues will come up on this distribution, and for that reason, they will be fixed by Arch contributors.<br /><br />Let us not try to pretend it is not Yocto's trade that they decided not to support this widely used distribution, officially.Laszlo Papphttps://www.blogger.com/profile/06121113102679268802noreply@blogger.comtag:blogger.com,1999:blog-2795663664308299225.post-62107208651103510582013-09-04T10:50:46.841-07:002013-09-04T10:50:46.841-07:00FWIW, I once made a contribution to util-linux bec...FWIW, I once made a contribution to util-linux because of something that broke in Arch (and would have broken in all the other distributions once they upgraded). I've known others who have done the same, possibly for Yocto as well.<br /><br />If you're not comfortable contributing fixes upstream, you shouldn't even be *using* Arch, much less developing it.<br /><br />That said, I gave up trying to build Dylan under Arch several months ago. I hack on Yocto as part of my job, and frankly, I didn't have the time for it. Since then I've used debootstrap to assemble an Ubuntu 12.04 chroot, then I do all my building via schroot. It works so marvelously that I don't really feel any need to do "native" builds anymore. Furthermore I think there are strong halo benefits to using chroots for these sorts of builds in general: as a developer, it's extremely useful to verify that something builds under several different distributions, and VM overhead (even using KVM) is somewhat high.<br /><br />*None* of that is Yocto's fault. The two biggest issues I ran into that were "Arch-related" were 1) texinfo-5.0 horribly broke binutils, 2) gcc-4.8 ICE'd on the gcc-4.7 build. Both were ultimately GNU's fault, not Arch's.<br />Richard Tollertonhttps://www.blogger.com/profile/01090397860437358524noreply@blogger.comtag:blogger.com,1999:blog-2795663664308299225.post-91144558432629109182013-07-26T13:05:51.135-07:002013-07-26T13:05:51.135-07:00This blog post is not about the Archlinux develope...This blog post is not about the Archlinux developer community, but the Yocto project itself.<br /><br />Off topic, but Archlinux developers sometimes contribute to upstream. I would like to give the credit for them when having done such well-done jobs.<br />Laszlo Papphttps://www.blogger.com/profile/06121113102679268802noreply@blogger.comtag:blogger.com,1999:blog-2795663664308299225.post-51081106594304736352013-07-26T01:38:12.610-07:002013-07-26T01:38:12.610-07:00I wouldn't expect ArchLinux developers to cont...I wouldn't expect ArchLinux developers to contribute to upstream software. Most of them are just package maintainers with no background in software development. You can tell by how most bugs are closed with "go report it upstream". There are some ArchLinux developers who can code software but they are simply busy.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2795663664308299225.post-82153714163987021102013-07-25T12:26:06.635-07:002013-07-25T12:26:06.635-07:00Hi suy,
thank you for your questions.
1) There h...Hi suy,<br /><br />thank you for your questions.<br /><br />1) There have been projects supporting arch. I believe it is the matter of focus. It is not hard to maintain it according to my experience. It is sometimes even simpler because they integrate bugfix and feature releases earlier than other distributions. That can help with many things, including the elimination of nasty workarounds around, et cetera.<br /><br />2) Not sure about how much luck we need. :)<br /><br />Yocto already runs on arch with master if I do not use either the cross-toolchain or the external Code Sourcery.<br /><br />This issue comes with the CS toolchain, but for desktop or perhaps even with internal toolchain, it could possibly work.<br /><br />3) I am currently using a Debian Wheezy (7.0) chroot, yes, but that also has its own quirks. However, that probably requires less expertise to solve than the Yocto or Mentor Graphics specific issues. In the meantime, I also devotee my spare time to collaborate with the Mentor Graphics and Intel employees to solve the critical Arch issues for once and all.<br /><br />4) I think one alternative is using a ready-made distribution, or just using a supported OS in chroot or virtualization. Luckily enough, at least debian stable is supported. The Mer Project is using scratchbox2 and OBS, but I prefer the Yocto/OE flavor, personally. I have never used buildroot myself, but I have read that it is not so much customizable, albeit I might be totally off there.Laszlo Papphttps://www.blogger.com/profile/06121113102679268802noreply@blogger.comtag:blogger.com,1999:blog-2795663664308299225.post-29615581151349607292013-07-25T10:58:51.077-07:002013-07-25T10:58:51.077-07:00Hi.
I'm quite a begginner with the embedded w...Hi.<br /><br />I'm quite a begginner with the embedded world, but let me comment on some things. First, how would Arch be supported? Wikipedia tells me is a rolling release distro, so how can that be supported something that is always moving?<br /><br />If you had the chance to attempt to install some of these tools on Arch, consider yourself lucky. I have an Ubuntu 10.04 virtual machine because I depend on an ancient LTIB installation provided by Freescale. Anything newer seems to displease an already fragile tool like LTIB. If you could do anything on a Debian chroot, I would totally change my place with you. :-)<br /><br />And besides, what do you think could be the alternatives? My first contact with embedded was such ancient LTIB, and the only tools that I hear that people like are ScratchBox2, BuildRoot and Yocto. And from what I've seen (again, I'm a newbie with this stuff), is easier if you surrender and use the same tool that the manufacturer suggests.<br /><br />Greetings.suyhttps://www.blogger.com/profile/10444402570029192627noreply@blogger.com