On Thu, Nov 12, 2015 at 3:24 AM, Parag Nemade <[email protected]> wrote:
> I also see most of the people participating this discussion are already > provenpackagers so they should be already having powers to update nodejs > packages in Fedora. That's a good point, and one that I've neglected to bring up. I'm a provenpackager, but until now I've hesitated to just go updating other people's packages without a very compelling reason. I know there's not a lot of technical difference between me updating a package as a provenpackager vs. me updating a package as part of a NodeJS packaging group -- but from a perception standpoint, I feel there's a difference. Maybe it's just me though... Along that same vein, though, I'll ask the question -- are people OK with me going through and updating some packages to the latest releases (assuming that the latest release still works on our current version of Node itself, and that it doesn't break the dependency chain on other packages)? For example, the COPR repo I mentioned earlier has updates to probably around 100 or so NodeJS packages in Fedora that I'm working on as part of my efforts to get some IoT tools packaged for Fedora. My selfish short-term goal is to get the apps packaged up in the COPR repo, but the longer-term goal is to get the updated packages pushed back into Fedora so that the apps themselves are packaged directly in Fedora. Also, I'm keen to get NodeJS 4.2 (LTS) packaged and working on Fedora, but that's probably a topic best suited to another mailing list thread. -- Jared Smith
_______________________________________________ nodejs mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/nodejs
