when adding packages to smart.json manually mrt should write them to .meteor/packages about meteorite

[jasonkuhrt]

+1

This will be a good ergonomic improvement.

I'll try to take a look at this within the next two weeks (if you don't beat me to it).

[tmeasday]

I guess....

Not sure about the removing though. What if a package is promoted to core? Then you'd remove it from smart.json and not from .meteor/packages.

I'm inclined to just leave this. It's not that big a deal (I think most people just mrt add X these days). It'll be resolved in some way when we integrate with core.

[jasonkuhrt]

@tmeasday mrt add x for the most part yes, except when working with local smart packages.

[tmeasday]

In which case you can be trusted to realise what's going on right?

[tmeasday]

I'm not objecting to the feature, just de-prioritizing it :)

[jasonkuhrt]

@tmeasday Actually my first time around, no, ha. 10 frustrating minutes later I did realize my mistake. But granted, the second, third, etc. time around I didn't make this mistake.

Regarding de-prioritizing it, I agree in the sense I would prefer if we made this issue a non-issue by improving mrt add. Allow local packages to be added like so:

mrt add meteor-angular Users/jasonkuhrt/code/meteor-angular. =)

[tmeasday]

Yeah, this is nice.

Open to pull requests :)

On Monday, 1 October 2012 at 12:30 PM, Jason Kuhrt wrote:

Oh, and then allow them to be removed like so:
mrt remove meteor-angular (let mrt figure out that this is a local package, not atmosphere)

—
Reply to this email directly or view it on GitHub (#44 (comment)).

[jasonkuhrt]

=) I've added this issue to my todos. I'm not a great or good programmer yet so low-hanging fruit is helpful for a peon like myself. I want to help I just can't do much, yet.

[sethburtonhall]

I am experiencing an error around this issue. I think...

When I create an app with

mrt create myapp

then I add the presence package with

mrt add presence

The presence package is installed in smart.json and smart.lock as normal, but it also installs the presence package within meteor/package. Then when I run my app, I get an error message saying

"presence package doesn't exist"

Why does this happen?

Has mrt always installed packages in the meteor/packages file?

Why is my app throwing the "presence package doesn't exist" error?

Thanks.

[sethburtonhall]

I am assuming that since this thread is suggesting mrt should automatically add packages to meteor/packages upon manual package load, that loading packages into meteor/packages has always been the normal.

Then why is the package not recognized? hmmm

[tmeasday]

@middle8media This sounds like a separate bug.

You say presence is in smart.json and smart.lock. Is there a symlink in .meteor/meteorite/packages ? Does stopping and starting your mrt server fix it?

[sethburtonhall]

Yes, there is a symlink.

I was running the server with meteor instead of mrt which was causing this weird behavior.

All is well now.