Repository, updates & new versions

been working my way through the rtfm on creating & developing extras & packages... though I am not seeing any information on updates & repositories.

- basically how does modx know that a package is an update & not a whole new extra?
- I see the modx upload page for packages, but how does the repository work? Say I wanted to create my own repository, how would I go about doing that?

-sean

- basically how does modx know that a package is an update & not a whole new extra?

To release an update you go to your package on the site and choose "Add new Version" in the sidebar instead of going to "Add new Extra" via the main nav

- I see the modx upload page for packages, but how does the repository work? Say I wanted to create my own repository, how would I go about doing that?

Not sure what you mean with a repository. If you mean a transport provider (so you can upload your own packages at a different url than modx.com) that's going to be a lot of custom development, which will be mostly pointless when the package manager gets reworked for 2.3 and all APIs and requests changed.

Quote from: markh at Mar 13, 2012, 12:26 PM

To release an update you go to your package on the site and choose "Add new Version" in the sidebar instead of going to "Add new Extra" via the main nav

Yes - I was trying to figure it out, normally I would have expected to have to include a little XML file or something in the transport package - but I guess that is all taken care of manually[??] by modx...

Not sure what you mean with a repository. If you mean a transport provider (so you can upload your own packages at a different url than modx.com) that's going to be a lot of custom development, which will be mostly pointless when the package manager gets reworked for 2.3 and all APIs and requests changed.

repository/provider ~ pardon my semantics I was just interested in getting a little more familiar with how they work out of interest mostly ~ I have no intention of setting up a provider....

-sean