[FLOW3-core] RFC: Replacing package.xml with composer.json

[Robert Lemke]

Hi Julle,

On 14.06.2012, at 07:44, Christian Jul Jensen <julle at typo3.org> wrote:

> In the process of refactoring package management to be fully composer
> compatible I need to change the handling of meta-data.
> 
> As far as I can tell package.xml is only used for versioning numbers
> which needs to be handled by composer anyway, so I am considering
> getting completely rid of it and using the composer manifest instead.
> 
> Any usecases that speaks against that?


Aside from refactoring the dependency resolution Andi mentioned, no.
Just go for it! You might want to add some code which - if no composer
manifest exists - checks if an old Package.xml exists and then extracts
the information from it and creates a basic composer file (so that at least
the name, package key, version etc. is saved).

Cheers,
Robert

-- 
Robert Lemke
Lead Developer TYPO3 Phoenix and FLOW3
Co-Founder TYPO3 Association

Blog: robertlemke.de/blog
Get involved: typo3.org – flow3.org



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2263 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/flow3-team-core/attachments/20120615/3d927135/attachment.bin>