While this might be overkill for your needs, I've used it in the past to maintain plugins retrieved via svn:externals. It's called Piston (http://piston.rubyforge.org/), and it allows you to keep a local copy committed to your own repository, but you can still update from the upstream repository referenced by svn:externals, and also make local modifications to your copy. It's kind of neat, and may be what you're looking for. In my opinion, it's the way svn:externals should work.
On Feb 1, 9:16 am, "Hassen Ben Tanfous" <[EMAIL PROTECTED]> wrote: > That's interesting. I like it :P > > Thanks > -Hassen > > On Feb 1, 2008 9:30 AM, Christian Schaefer <[EMAIL PROTECTED]> wrote: > > > > > Hi Hassen, > > > well you could of course use PHP inside the schema.yml to set stuff > > according to some other yml like your local app.yml. > > > cheers > > /Christian > > > On 1 Feb., 14:22, "Hassen Ben Tanfous" <[EMAIL PROTECTED]> > > wrote: > > > Hello Christian, > > > I was referring to the schema.yml > > > > cheers > > > -Hassen > > > > On Feb 1, 2008 4:05 AM, Christian Schaefer <[EMAIL PROTECTED]> wrote: > > > > > hi hassen, > > > > > why would you want to modify the original code? > > > > wouldn't it be far more elegant to extend the class in each of your > > > > projects? > > > > > cheers > > > > /christian > > > > > On 31 Jan., 23:36, "Hassen Ben Tanfous" <[EMAIL PROTECTED]> > > > > wrote: > > > > > Hello, > > > > > I'm having a small issue. Let's say I'm using the sfGuardPlugin. I > > > > > download on my SVN, add it to my plugins directory and set it as a > > > > > svn:external on all my projects. > > > > > > Let's say I'm referencing this sfGuardPlugin on 4 symfony projects. > > On > > > > > project x, y, z I've a user table and on project foobar I've an > > artist > > > > > table. > > > > > I want the foreign key (defined in the plugin) to point to the user > > > > table > > > > > for the projects x, y z and on artist for the project foobar > > > > > > Is there a way to be able to update the code only once (using > > > > svn:externals) > > > > > and keep the plugin compatible with all projects even when it needs > > some > > > > > tweaking like changing a foreign key reference? > > > > > > Maybe having an alias? In the plugin we call it user_id but > > depending of > > > > the > > > > > project, I can set the value of the alias to whatever I want. > > > > > > Of course, at the moment, the easiest solution is to duplicate the > > code > > > > and > > > > > next time I want to update the plugin, I'm f*. > > > > > > Thanks > > > > > Sincerely > > > > > -Hassen --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
