Andy Pieters schrieb: > Is there anyone that can provide a solution to this or suggest another > approach to the problem? First of all something about packages: PEAR is coming up with their own format ".phar" for this. These are tar archives that may contain an additional PHP script that is executed when unpacking the archive. This gives you all the possibilities of other package management systems. If you decide to go for standard package formats: I can't tell you anything about .rpm but I know that it isn't too difficult to build .deb packages. There are good howtos for the debian format. As another approach: How about using Subversion? PHP developers have one advantage: They don't have to compile their code before deployment. So in other words: Deployment is somehow very similar to just getting the source code. Subversion on Apache allows for easy access control. You cann create a deployment branch or even different branches for each of your customers. After you have created some new features in your project you can simply merge the changes to your braches. All the client has to do to fetch this update is one single "svn up"! OLLi -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
