oortcloud / meteorite

Installer & smart package manager for Meteor
http://oortcloud.github.com/meteorite/
MIT License
841 stars 106 forks source link

Error on installing Meteor 0.9.0 packages #296

Closed nerdmed closed 10 years ago

nerdmed commented 10 years ago

Hey Team,

as i am testing to change my packaging enviroment to the new packaging system i still need to have private repositorys for non-public packages that are shared across projects. I updated the package to fit the requirements Meteor has for new packages. But after adding them inside my smart.json and running:

mrt add package:name

it will download the package but then error me with:

/usr/local/lib/node_modules/meteorite/lib/command.js:57
        throw "Command exited: " + error;
                                 ^
Command exited: Error: Command failed: --using: unknown option.
Usage: meteor list

List the packages that you have explicitly added to your project. This will not list transitive dependencies.

Would be great to have it afterwards auto added to the project by running meteor add package:name

apendua commented 10 years ago

@nerdmed Can you check your mrt version. If it's < 0.9.0 then you need to update. Also make sure that your meteor is the latest one, so run meteor update.

nerdmed commented 10 years ago

Hey @apendua thanks for your response. For me the versions are:

mrt --version
>Meteorite version 0.9.0
>Meteor 0.9.0

I think this is correct. As i mentioned the error will produce if you try to install a package that is on a git repository via mrt and adding it into the smart.json

tmeasday commented 10 years ago

Hey @nerdmed -- no you are right, this is a bug with Meteorite.

However, I would discourage you from using mrt add from now on. You can still add packages to smart.json (with a git URL, I assume this is what you are doing?), mrt install them, then meteor add them. Does that solve the problem?

nerdmed commented 10 years ago

Hey @tmeasday thanks for your reply! You are right i am adding the git URL in my smart.json because of private packages. Your solution works well. This broblem is hardly related to this post in the google meteor-core group would be great to hear from you.