On 03/13/2013 10:47 PM, T.C. Hollingsworth wrote:
Like the equivalent many other languages, Node.js C++ extension
modules result in unwanted provides that by policy need to be
filtered, We definitely want to provide a %nodejs_default_filter
similar to Perl's %perl_default_filter to make this easy for
However, I understand the old guidelines are outdated, and Perl's
macro already uses the new version . Should we go ahead and use
the new version too when implementing %nodejs_default_filter or wait
for the draft to be approved?
packaging mailing list
I would use the new macro. I guess the old one won't work anyway with
I wonder if you have any automatic packaging script, which can turn
modules into srpms, so you could add the filtering macro automatically
into the specfile.