On 28.07.2011 17:23, Johannes Schmitt wrote:
> That's what I did, but I need to declare some dependencies in almost all
> of my bundles :)
> 
> Anyway, the question remains, does it make sense to include it, at all?
> Is the format final or still subject to changes?

Some minor details aren't set in stone yet, but generally field names
should not change, it's all quite inspired from npm & gems, so I don't
expect too many issues.

I would say it's nice to include them already, because then we have a
bigger test base while working on the code. So if you depend on symfony,
the idea would be that you mark it as Symfony >=2.0.0 in your 1.0.0 tag,
then if your 1.1.0 tag has Symfony>=2.1.0, and the installed version of
symfony is 2.1, it shouldn't pick your 1.0.0 tag.

Anyway that's the main contention point left I think, how to describe
versions. I'll hopefully find some time this week to document some more
stuff and communicate a bit on this whole thing.

> On Thu, Jul 28, 2011 at 5:20 PM, Christophe COEVOET <s...@notk.org
> <mailto:s...@notk.org>> wrote:
> 
>     Le 28/07/2011 17:17, Johannes Schmitt a écrit :
> 
>         Could someone shed some light on whether it makes sense to
>         already include the composer file (like it is done in Monolog),
>         and if so how it should look like?
> 
>         Johannes
> 
>     You can look at Monolog for an example (a simple one as Monolog does
>     not have any dependency except PHP)

Yes, Monolog contains a simple one. Should be enough for most purposes,
but you can also look at http://packagist.org/packages.json which
contains a bit more data (which are implicitly added if missing, like
the source, time or dist).

Cheers

-- 
Jordi Boggiano
@seldaek - http://nelm.io/jordi

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en

Reply via email to