https://bugzilla.redhat.com/show_bug.cgi?id=1132661 --- Comment #44 from Mike Goodwin <mike@xxxxxxxxxxxx> --- Packaging atom isn't even remotely a possibility until electron is able to be built on koji. It seems the gentoo guys figured out how to build it at least: https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-util/electron/electron-1.3.13-r1.ebuild This is a massive undertaking that will likely needs its own SIG/Community surrounding it and the current chromium builds. (poor tom) There are hundreds of electron based apps out there that are ripe for packaging, imho. My personal interest is for Rocket.Chat.Electron. None of this is going to see any fruition until their foundation (electron) is through review and able to be consistently maintained. One of the biggest problems that I can tell is that the chromium/libchromiumcontent/electron instructions are based on pulling all sorts of precompiled nonsense from their entire ecosystem - something which I guess is to be expected from a chromium based project. This won't fly here, and as such it needs to be torn down a re-done to be able to be packaged with what's available to koji (and would probably have to be heavily based on the efforts of @spot in packaging chromium) - as it stands I couldn't even get electron to pass the bootstrap and/or build phase based on the instructions they provide (https://github.com/electron/electron/blob/master/docs/development/build-instructions-linux.md) and that includes allowing it to pull all of the bundled material. It's honestly suspect whether there are more than a handful of people out there right now that can actually build it, it seems. The next hurdle after that is going to be in automating and packaging the (what im sure are hundreds) of node dependencies needed by atom, and after that, unbundling atom and getting it to use all the previously mentioned efforts properly. I highly doubt any one person will undertake these tasks in order to actually packaged this monstrosity in such a way that would actually pass review, unless we amass a significantly large community of people willing to work on it. I'm not holding my breath, though. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
