enhancement - some guidance in documentation as to how to package source should be updated

[deborah-ufw]

I just created and published a package, then marked it as private and added it to my app. :)

Now I want to tweak my package, of course!

Looking in the documentation for Atmosphere, I don't see any guidance on how to update package source for Atmosphere, whether it's public or private...

• when adding a package, does it automatically add it from the up-to-date Github repo where the source code is stored?
• or do I need to re-publish the updated package to Atmosphere? Then do I need to re-mark it as private using "meteor admin set-unmigrated"? Is there anything else I need to do?
• how do I version a package, or is there any need to do so?
• in my Meteor app, assuming the package source has been correctly updated, does "meteor update" automatically capture that the package is updated, and update it? Alternatively, does it notify user that a new version has been detected and should be updated specifically? If not, how does package creator enable this?

Some verbiage surrounding this would be very helpful for a Meteor and package newbie, both on the "Publish Packages" page and possibly in "FAQ".

Thank you very much for awesome Atmosphere!

[tmeasday]

Hi @deborah-ufw,

I suspect you may want to read https://guide.meteor.com/writing-packages.html

Some answers:

when adding a package, does it automatically add it from the up-to-date Github repo where the source code is stored?

No. This field is just used for documentation / so people can look up the source code.

or do I need to re-publish the updated package to Atmosphere? Then do I need to re-mark it as private using "meteor admin set-unmigrated"? Is there anything else I need to do?

set-unmigrated isn't really intended for "private" packages (I mean they aren't really private, right?). But, yes, you would need to re-publish and set-unmigrated.

how do I version a package, or is there any need to do so?

I would expect so but I don't really understand the usecase properly.

in my Meteor app, assuming the package source has been correctly updated, does "meteor update" automatically capture that the package is updated, and update it? Alternatively, does it notify user that a new version has been detected and should be updated specifically? If not, how does package creator enable this?

meteor update will get the latest version.

[deborah-ufw]

Thank you tmeasday :)

I was just reading the Meteor package documentation here and seeing that some of the answers to my questions were there. I'll also check out the link you provided. Looks like the answers are probably all available (it would be nice to have the links in the Atmosphere docs too).

I'm finding there are a lot of pieces of Meteor's documentation scattered around in different places. Eventually I'll get the hang of where to find what. Thanks!