On Jan 9, 9:43 am, "Tristan Rivoallan" <[EMAIL PROTECTED]>
wrote:
> hi,
>
> On Jan 9, 2008 12:56 AM, Carl Vondrick <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Tuesday, January 08, 2008, Jonathan Wage wrote:
> > > I think if it were included in the core it would need to be rewritten to
> > > symfony standards :) A lot of things could be better/different.
> > Yes, of course.
>
> > I think it would be particularly "cool" if the task could optionally
> > automatically communicate with symfony's server to automatically upload
> > the
> > plugin, albeit unrealistic to implement.
>
> not *that* unrealistic : python's setuptools interface really well
> withhttp://pypi.python.org/pypi
> since trac has an XMLRPC interface, it would probably be not too difficult
> to provide the same level of functionality.
The PEAR tools already provide an API for that (and many other remote
operations). As long as you have a pear server/channel, it is
relatively easy to implement. I can give a hand if needed, I'm only
trying to figure who does what and where. The forge, not forge,
symfony/extern areas are rather confusing these days :)
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
