Link non-core packages at meteor/packages

[TomFreudenberg]

In case of some errors and frustrations during first contact to meteor, it might be a good idea to create links to non-core packages at meteor/packages path during installation.

Read more about circumstances on already closed issue #1 (comment) and on meteor universal blog http://meteor-universal.tumblr.com/post/111435518849/use-non-core-packages-for-your-meteor-apps

Currently not sure if it fits to MDG rules or not to create those links during installation. Will try to figure this out.

[TomFreudenberg]

This is not done automatically but added a script for easy linking all not referenced non-core packages.

[TomFreudenberg]

ATTENTION !!! As from a comment from MDG you SHOULD NOT link the non-core packages directly inside the packages directoy of a checkout meteor.

The correct advise is:

# setting the env var 
export PACKAGE_DIRS=<your meteor checkout path>/packages/non-core

If this is not suitable for you, you still may link the non-core package to your project

cd <your meteor app path>/packages
ln -s <your meteor checkout path>/non-core/npm-bcrypt .