OK, that's what I thought ;)
Thanks !
On 23 avr, 08:35, Fabien Potencier <fabien.potenc...@symfony-
project.com> wrote:
> naholyr wrote:
> > Hello,
>
> > I published packages for a plugin with 2 branches : this is the same
> > "version" of the plugin as features and API are exactly the same, but
> > this is not for the same version of Symfony, so I must publish
> > different packages (one for each version of Symfony).
>
> > -> When I publish those packages as being from the same version, it
> > fails saying there is already a release with this name.
>
> Yes, you can obviously only have one package with a given version.
>
> > -> When I publish the packages with different version numbers, it
> > seems to work but on the plugin's web page I see it as being available
> > only for Symfony 1.2 as it displays only the last version and I use
> > numbers x.y.z where x.y is the branche of Symfony.
>
> The latest (the greatest version number) version is the one shown by
> default, whatever the symfony version it is for.
>
>
>
> > What's the best way to do it (having more than one branch of the
> > plugin, packaged under the same version numbers) ?
>
> The way it works now is sub-optimal but this is the only way because of
> the way PEAR works.
>
> Fabien
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---