search

oortcloud / meteorite

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

Update single package #176

Open subhog opened 11 years ago

subhog commented 11 years ago

I'm working on a package and app that uses it at the same time. After I publish changes in the package, it would be useful to update the package version in the app. Currently, as far as I know, this can be only done by mrt update. However, this command tries to update every package used, which is long and often unwanted. It would be really handy to be able to write mrt update packagename.

tmeasday commented 11 years ago

Yes, this would be nice to have, but if I remember rightly, is non-trivial to implement.

subhog commented 11 years ago

Now this became especially important, as I want to update my package, but due to other dependencies cannot switch to 0.6.5 just yet.

What is the problem with this functionality? Is it due to possible dependencies, or is there something else?

tmeasday commented 11 years ago

mrt update won't switch you to 0.6.5.

harlio commented 10 years ago

+1 for mrt-update packagename not updating every package. Potentially problematic to determine which package is causing bugs or breaks if you don't have better control over version updates. At the very least when mrt update is running, outputting a line in the log letting you know what version the package was update from along with the new package version would help when determining which stable package version to revert to using --pkg-version.

Currently:

✓ template-animation-helper
    tag: https://github.com/frozeman/meteor-template-animation-helper.git#v0.3.6

Proposed:

✓ template-animation-helper
    old tag: https://github.com/frozeman/meteor-template-animation-helper.git#v0.2.3
    new tag: https://github.com/frozeman/meteor-template-animation-helper.git#v0.3.6
tmeasday commented 10 years ago

Hey Harley,

You can get this information from smart.lock (do a git diff perhaps)

El 10 Dec 2013, a las 6:18 am, Harley Jessop notifications@github.com escribió:

+1 for 'mrt-update packagename' not updating every package. Potentially problematic to determine which package is causing bugs or breaks if you don't have better control over version updates. At the very least when 'mrt update' is running, outputting a line in the log letting you know what version the package was update from along with the new package version would help when determining which stable package version to revert to using '--pkg-version'.

Currently: ' ✓ template-animation-helper tag: https://github.com/frozeman/meteor-template-animation-helper.git#v0.3.6 '

Proposed: ' ✓ template-animation-helper old tag: https://github.com/frozeman/meteor-template-animation-helper.git#v0.2.3 new tag: https://github.com/frozeman/meteor-template-animation-helper.git#v0.3.6 '

— Reply to this email directly or view it on GitHub.

harlio commented 10 years ago

Thank you. I already knew about the info in smart.lock, mostly I just think that giving some visual cue that a package has been updated when running mrt update (at least for as long as its going to happen automatically like this) would be a better alternative than NOT notifying about a package update. That being said, ideally it would be nice to have control over which packages get updated and which ones don't, as I think that feature would lend the most to making Meteor environments using Meteorite packages more stable.