I'd be very interested in going in reverse, i.e. feeding a package.xml in and generating a composer.json
I think this would help with two things:
Smooth the learning curve for developers that are already releasing on Magento Connect.
Bring composer support closer for extensions that are on Magento Connect only.
I believe these two points would help with the adoption of composer for package management in Magento.
Ideally hook into composer.phar for the cli to generate this; similar to composer.phar init.
Either work on a directory in the local file system or a Magento Connect key (e.g. download, extract and create the composer.json)
The mappings enabled by package.xml and magento-composer-installer would obviate the need for a modman file to do the mapping - not that I have anything against modman it just wouldn't be required.
I'd be happy to sponsor this development so if you're interested please get in touch with me.
I'd be very interested in going in reverse, i.e. feeding a
package.xml
in and generating acomposer.json
I think this would help with two things:
I believe these two points would help with the adoption of composer for package management in Magento.
Ideally hook into
composer.phar
for the cli to generate this; similar tocomposer.phar init
. Either work on a directory in the local file system or a Magento Connect key (e.g. download, extract and create thecomposer.json
)The mappings enabled by
package.xml
and magento-composer-installer would obviate the need for amodman
file to do the mapping - not that I have anything against modman it just wouldn't be required.I'd be happy to sponsor this development so if you're interested please get in touch with me.