Composer support?

Yii 2.0 General Discussions
1

How about composer support to yiic and mandatory for extensions?

http://packagist.org/about-composer

2

I’m evaluating it and it looks like a good idea. Alternatives are:

  1. Use your own package manager.

  2. Use another package manager.

3

A post from the creators explaining the "What & Why" of project:

http://nelm.io/blog/2011/12/composer-part-1-what-why/

4

Looks very promising :)

5

Yes, I saw it. Yii2 is PSR-0 compatible so using this package manager will not be a problem. The only question is should it be official one or not.

6

Umh… Composer requires PHP v5.3+. Isn’t Yii 2.0 supposed to require v5.2+? How much of a problem would that be?

7

Yii 2 will require 5.3 as well.

8

That’s the advantage, by including it in the core we enforce some rules in the extensions community and an easy way to install them.

Because we can use it with yii right now, if someone want’s it.

9

Composer really looks like a great idea. :)

10

Sounds very similar to the approach jQuery is taking for plugins.

if you skip down to the "nuts and bolts" bit:

http://blog.jquery.com/2011/12/08/what-is-happening-to-the-jquery-plugins-site/

11

It could be based on it so that it can be compatible on a lower level, but I want would like to have added support for module/extension specific migrations. :)

12

+1 for Composer.

13

I think that could be advantageous for us(at least for avoiding dependency hell), so +1 for this idea.

14

Hi,

as for repository management tool, all alternatives should be objectively considered.

Options currently might be:

[list=1]

[*]Composer (wrapper for phar extension)

[*]PHPCR (https://github.com/midgardproject/phpcr-midgard2)

As far as I understand, this is a PHP port of original standardized Java web content repository system.

More: http://bergie.iki.fi/blog/midgard2_phpcr_provider_hits_1-0/

[*] own Yii designed repo management tool

[/list]

Regards

Lubos

15

I think Composer is primary candidate to be a “package manager”. It’s very configurable, already has fast-growing packagist.org repo.

16

lubosdz

Frontend for PHPCR is still composer ;)

17

PHPCR is something entirely different as it defines an API that covers the storage needs of a CMS (essentially a NoSQL DB with versioning, tree/graph traversal, ACLs and full text search).

18

FYI, I let the composer core team know about the interest. Unfortunately they of course cannot access this forum, so they cannot comment. If you have questions or concerns, I guess you know how to get in touch with them.

19

Thanks.

20

I support the composer approach. +1