Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecation warning #264

Open
dandv opened this issue Mar 19, 2014 · 2 comments
Open

Deprecation warning #264

dandv opened this issue Mar 19, 2014 · 2 comments

Comments

@dandv
Copy link
Member

dandv commented Mar 19, 2014

As far as I can tell, when mrt installing a deprecated package, perhaps from inherited codebase, the user has no indication that a package is deprecated. Right now, the only way to check that a package might be deprecated is to look at its README.

Does meteorite/MDG have plans for a "deprecated" flag that would warn on install, and perhaps point to an alternative package, or a resource for more information?

@tmeasday
Copy link
Member

My understanding is that packages will be explicitly tied to meteor versions that they have been marked to work with. So deprecation will happen implicitly when an author fails to keep the package up to date with new versions.

We'll find out more at devshop this month I guess :)

@dandv
Copy link
Member Author

dandv commented Mar 25, 2014

Good point. The deprecation use case I had in mind was when an author wants their package to stop being used on purpose, e.g. because a better package has emerged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants