Re: [RFC] Extension Prepend Files

Hi! > The first reason is that, if we consider a released extension as a > conceptual unit, the best way to protect its integrity is to store it > as a single file. Storing it as separate files brings a lot of > potential issues : files can be renamed, deleted, etc. Offline tools Yet people have been releasing mulfi-file software packages for decades, and it seems to work fine and the software world has yet to collapse under these problems. Which suggests they maybe not as severe as they seem to be. > code. But, if we consider the PHP code as an integral part of the > extension, this should be avoided, as C and PHP code need to be kept > in sync. Again, there is a multitude of solutions for this, all in the realm of packaging. It's not like we've just encountered the idea of software package having more than one file. -- Stas Malyshev smalyshev@gmail.com