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 packagers.
However, I understand the old guidelines are outdated, and Perl's macro already uses the new version [1]. Should we go ahead and use the new version too when implementing %nodejs_default_filter or wait for the draft to be approved?
Thanks! -T.C.
[1] https://fedoraproject.org/wiki/User:Toshio/AutoProvidesAndRequiresFilteringD...
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 packagers.
However, I understand the old guidelines are outdated, and Perl's macro already uses the new version [1]. Should we go ahead and use the new version too when implementing %nodejs_default_filter or wait for the draft to be approved?
Thanks! -T.C.
[1] https://fedoraproject.org/wiki/User:Toshio/AutoProvidesAndRequiresFilteringD...
packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
I would use the new macro. I guess the old one won't work anyway with latest rpm. 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.
Marcela
On Mar 26, 2013 8:01 AM, "Marcela Mašláňová" mmaslano@redhat.com wrote:
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 packagers.
However, I understand the old guidelines are outdated, and Perl's macro already uses the new version [1]. Should we go ahead and use the new version too when implementing %nodejs_default_filter or wait for the draft to be approved?
Thanks! -T.C.
[1]
https://fedoraproject.org/wiki/User:Toshio/AutoProvidesAndRequiresFilteringD...
-- packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
I would use the new macro.
+1
As a side comment, the new guidelines were one vote shy of passing last I looked (with no negative votes).
-Toshio
packaging@lists.fedoraproject.org
-
Marcela Mašláňová -
T.C. Hollingsworth -
Toshio Kuratomi