If forced retirement of node-waf is the goal, can you just release a new version of it that either is a wrapper for node-gyp or whines bitterly whenever it's used? Could even make it "phone home" to tell the package author what they need to change. Seems like this would be easier than tracking down all the node-waf dependents by hand.
--Ken -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
