Question

• I have a PHP Platform that I’ve built.
• I use a copy of that project for each project I do.
• I add assets and configure each project with it’s own content.
• Configuring a project changes some of the core files which contain
  the configuration defaults.

When I update core files in the library/platform itself and I want to disseminate those changes to all of the other projects using that platform, what would be the best approach?

I think it may be worth noting that I have each project as an SVN project in Eclipse.

UPDATED DETAILS:

• The platform is based on AMFPHP 1.9.
• AMFPHP has a services folder.
• I have to put core services in the services folder as well as
  implementation specific services and therefore cannot achieve
  complete separation between the “library” and the “application”.
• Also, the default configuration files need to be in the “platform” folder
  so they can be easily distributed with it, but when configuration is
  changed, those files become “implementation specific” as well.

Is there a solution that will allow me to designate certain files to update?

Answer 1

Take a look at the use of svn:externals. Configure each secondary project with your core libraries as an external.