https://bugzilla.redhat.com/show_bug.cgi?id=1132661 --- Comment #22 from Mohammed Safwat <Mohammed_ElAfifi@xxxxxxxxx> --- I noticed the fact that electron was downloaded as an archive at some step during the build process. I was planning to package electron for this purpose so that atom may be made dependent on it. I spent some time looking at the build scripts of atom. The problem isn't much about packaging grunt-* tasks as it's about packaging dependencies listed in the dependencies key here https://github.com/atom/atom/blob/v1.6.2/package.json. I don't know how deep this might go, as each npm package may have its own dependencies and so on. The alternative is to bundle these dependencies with atom package, which mightn't be very welcome by FPC. Now coming to the concerns raised by sensor.wen, it seems even electron can't be packaged as there're still offending issues with libchromiumcontent(or chromium, whatever, I'm not an expert here so I'm just quoting sensor.wen's remarks). Don't know either about the necessity of separating atom and apm but given the apparently pending problems with electron, have we reached a dead end? -- 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 http://lists.fedoraproject.org/admin/lists/package-review@xxxxxxxxxxxxxxxxxxxxxxx