I figured you would need commit access to fix any problems with the package.xml.
I am pretty sure a developer can packager too? If you can't have access to svn and be a packager without being a project leader then it sounds like that might need to be fixed. - Jon On Thu, Apr 16, 2009 at 1:26 PM, Tom Boutell <t...@punkave.com> wrote: > > Looks like you made me a developer, not a packager... > > On Thu, Apr 16, 2009 at 1:52 PM, Jonathan Wage <jonw...@gmail.com> wrote: > > Ok. Request access and I'll accept. > > > > - Jon > > > > On Thu, Apr 16, 2009 at 12:47 PM, Tom Boutell <t...@punkave.com> wrote: > >> > >> Sure! > >> > >> On Thu, Apr 16, 2009 at 1:44 PM, Jonathan Wage <jonw...@gmail.com> > wrote: > >> > How would you feel about me giving you access to sfDoctrineGuardPlugin > >> > as a > >> > packager and you can help me with maintaining the packages? :) That > >> > would be > >> > very helpful. > >> > > >> > - Jon > >> > > >> > On Thu, Apr 16, 2009 at 8:37 AM, Tom Boutell <t...@punkave.com> wrote: > >> >> > >> >> I think I may have found it. > >> >> > >> >> None of the sfDoctrineGuardPlugin package.xml files indicate what > >> >> version of Symfony they require. Which is surprising, and it made me > >> >> wonder how the heck the Symfony site knows what version of Symfony > >> >> they are for. > >> >> > >> >> When I dig a little deeper I see that the 1.x and 2.x versions of > >> >> sfDoctrineGuardPlugin *do* indicate what version of the > >> >> sfDoctrinePlugin they are for, although they say nothing explicit > >> >> about Symfony itself. > >> >> > >> >> But the 3.x version (3.0.0) says nothing at all about either Symfony > >> >> or sfDoctrinePlugin. > >> >> > >> >> I suspect that Fabien's code for the plugins site is inferring the > >> >> appropriate version of Symfony from the version of Symfony that the > >> >> required sfDoctrinePlugin is associated with. > >> >> > >> >> I'm still not sure how the plugins site is deciding to list the 3.0.0 > >> >> version as "for Symfony 1.2," but my suspicion is that it's just the > >> >> default in some of Fabien's code. But not in all of it, which is why > >> >> the 3.0.0 version is never offered to satisfy a dependency in another > >> >> plugin. I think. There's still something funny about that I admit, > >> >> seeing as my plugins are calling for it specifically by version > number > >> >> range. > >> >> > >> >> Jon, I suggest you add: > >> >> > >> >> <package> > >> >> <name>symfony</name> > >> >> <channel>pear.symfony-project.com</channel> > >> >> <min>1.2.0</min> > >> >> <max>1.3.0</max> > >> >> <exclude>1.3.0</exclude> > >> >> </package> > >> >> > >> >> To the <required> section of your package.xml and see if that enables > >> >> an attempt to 'plugin install sfDoctrineApplyPlugin' to find and use > >> >> the sfDoctrineGuardPlugin package as a dependency in a Symfony 1.2 > >> >> project. > >> >> > >> >> (Fabien, does your "strict" checkbox check for this kind of > >> >> requirement? If there is such a requirement...) > >> >> > >> >> On Wed, Apr 15, 2009 at 6:31 PM, Jonathan Wage <jonw...@gmail.com> > >> >> wrote: > >> >> > Do the licenses of the plugins have to be the same in order to use > >> >> > them > >> >> > as > >> >> > dependencies? That is the only thing I see different. > >> >> > > >> >> > - Jon > >> >> > > >> >> > On Wed, Apr 15, 2009 at 3:26 PM, Tom Boutell <t...@punkave.com> > wrote: > >> >> >> > >> >> >> I'm packaging pkContextCMSPlugin again and looking to do the > >> >> >> dependencies right this time. > >> >> >> > >> >> >> I set this up in the required block of packages.xml: > >> >> >> > >> >> >> <package> > >> >> >> <name>sfDoctrineGuardPlugin</name> > >> >> >> <channel>plugins.symfony-project.org</channel> > >> >> >> <min>3.0.0</min> > >> >> >> <max>4.0.0</max> > >> >> >> <exclude>4.0.0</exclude> > >> >> >> </package> > >> >> >> > >> >> >> When I try to install my package I get: > >> >> >> > >> >> >> >> sfPearFrontendPlugin Failed to download > >> >> >> >> symfony-plugins/sfDoctrineGuardPlugin > >> >> >> >> sfPearFrontendPlugin (version >= 3.0.0, version <= 4.0.0, > >> >> >> >> excluded > >> >> >> >> versions: > >> >> >> >> sfPearFrontendPlugin 4.0.0), latest release is version 2.0.1, > >> >> >> >> stability > >> >> >> >> "stable", > >> >> >> >> sfPearFrontendPlugin use > >> >> >> >> sfPearFrontendPlugin > >> >> >> >> > >> >> >> >> "channel:// > plugins.symfony-project.org/sfDoctrineGuardPlugin-2.0.1" > >> >> >> >> to > >> >> >> >> install > >> >> >> > >> >> >> But there is an sfDoctrineGuardPlugin 3.0.0, and it is a stable > >> >> >> release. > >> >> >> > >> >> >> I could've sworn the same thing worked for sfDoctrineApplyPlugin, > >> >> >> which is where I copied and pasted it from. I put in a lot of time > >> >> >> last month on this mailing list making sure that worked. But to my > >> >> >> surprise, you can't install that plugin into a new project anymore > >> >> >> either. Same error. > >> >> >> > >> >> >> I have cleared the pear cache. Heck, I've used an entirely new > >> >> >> Symfony > >> >> >> 1.2 project for each test. > >> >> >> > >> >> >> When I go to the sfDoctrineGuardPlugin page it does list 2.0.1 for > >> >> >> symfony 1.1 as the current release. But the releases page shows > >> >> >> 3.0.0 > >> >> >> for symfony 1.2 as a stable release. > >> >> >> > >> >> >> I have checked symfony --version, it's 1.2.6 DEV, I'm not > >> >> >> accidentally > >> >> >> running 1.0 or 1.1. > >> >> >> > >> >> >> Is this an issue with the packaging of sfDoctrineGuardPlugin, or > >> >> >> with > >> >> >> plugin:install, or...? > >> >> >> > >> >> >> -- > >> >> >> Tom Boutell > >> >> >> P'unk Avenue > >> >> >> 215 755 1330 > >> >> >> punkave.com > >> >> >> window.punkave.com > >> >> >> > >> >> >> > >> >> > > >> >> > > >> >> > > >> >> > -- > >> >> > Jonathan H. Wage > >> >> > Open Source Software Developer & Evangelist > >> >> > http://www.jwage.com > >> >> > http://www.doctrine-project.org > >> >> > http://www.symfony-project.org > >> >> > > >> >> > > > >> >> > > >> >> > >> >> > >> >> > >> >> -- > >> >> Tom Boutell > >> >> P'unk Avenue > >> >> 215 755 1330 > >> >> punkave.com > >> >> window.punkave.com > >> >> > >> >> > >> > > >> > > >> > > >> > -- > >> > Jonathan H. Wage > >> > Open Source Software Developer & Evangelist > >> > http://www.jwage.com > >> > http://www.doctrine-project.org > >> > http://www.symfony-project.org > >> > > >> > > > >> > > >> > >> > >> > >> -- > >> Tom Boutell > >> P'unk Avenue > >> 215 755 1330 > >> punkave.com > >> window.punkave.com > >> > >> > > > > > > > > -- > > Jonathan H. Wage > > Open Source Software Developer & Evangelist > > http://www.jwage.com > > http://www.doctrine-project.org > > http://www.symfony-project.org > > > > > > > > > > > -- > Tom Boutell > P'unk Avenue > 215 755 1330 > punkave.com > window.punkave.com > > > > -- Jonathan H. Wage Open Source Software Developer & Evangelist http://www.jwage.com http://www.doctrine-project.org http://www.symfony-project.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
