On Wed, Jun 27, 2012 at 1:45 PM, Isaac Schlueter <[email protected]> wrote:
> What we're seeing in practice is just weird and broken behavior,
> usually because an old version of something (say, a package from 2
> years ago, which doesn't work on modern node) might have no engines
> specified, but a newer version of the same package (which works fine
> on 0.8) has "engines":{"node":"0.6.x"} specified. So, npm tries to
> find the most recent version that it thinks will work, and it gets
> 0.1.2 (which is broken and old) instead of 4.8.12 (which is new, and
> works). That's the opposite of the intent. A nag would be more
> appropriate in that case, I think.
>
What CPAN does is always get the most recent, and if it fails because of a
reason like this (in Perl terms, the Makefile.PL has a "use <version>"
tag), it just fails. To get an older version you have to ask for that
version specifically. Would this not work here?
--
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
