http://packages.firegento.com/ outdated

[akorsus]

Hi,

I thought the Connect 2.0 packages on http://packages.firegento.com/ get updated automatically, but e.g. http://www.magentocommerce.com/magento-connect/locale-mage-community-de-de.html has the version no 1.7.0.2.4 versus 1.7.0.2 on http://packages.firegento.com/

The same with e.g. http://www.magentocommerce.com/magento-connect/turpentine-6332.html

[Flyingmana]

the connect 2.0 packages are managed separate from the firegento list.
Iam not sure they get updated automatically, maybe @thebod can answer this.

[real34]

Is there anything we can do to help with this automatic update?
We have not found how http://connect20.thebod.de/ is generated / updated

[Flyingmana]

the scripts for updating the connect repository are not public, as they use no official API.
And they also run not automatic, as they create some heavy usage.

The best you can do to solve this for the future is to ask @magento for offering an official composer repository.

Under the current circumstances there will always be outdated connect packages, but we try to update them at least if a new mage release got out.

[real34]

Thanks for your answer, I noticed versions have been updated.

However without further @magento support, would it be possible to allow PRs to be made on the packages.json? It would be the best of both worlds: allowing users to contribute by updating versions of the most used modules without waiting the "resource expensive script" to be run.

[Flyingmana]

the best way to contribute up to date modules to this repository is to offer them via a vcs, so we can add them to https://github.com/magento-hackathon/composer-repository/blob/master/satis.json
We accept pull requests for this file.