On 08.03.2011, at 00:04, Lukas Botsch wrote: > Hi Nils, hi Bernhard! > > I had exactly the same idea some weeks ago and started a project named > SymfonyBundler (https://github.com/SymfonyBundles/SymfonyBundler) > It is in very early state and lacks of a documentation. If you are > still interested in this, I would love to read about your ideas... > > The concept of SymfonyBundler is as simple as it could be: > - A bundle manifest/descriptor structure (xml based) which defines > version and dependencies of a bundle. > - An abstract repository interface that could be implemented using > git, svn, http, ftp, etc... > - A bundler configuration file that defines the bundles (and bundle > sources) to use in one project > - An extension to the AppKernel that registers the bundles and their > dependencies > - An extension to the Autoloader that registers the bundle namespaces > to the UniversalClassLoader > - Console commands to manage bundles (install/update/etc...) > > I will try to write some documentation in the next few days... > Also have a look at http://symfonybundles.github.com/#Bundler for some > thoughts on the subject and soon for the documentation...
one very appealing thing is to make it possible to use the package manifest but still checkout from an SCM. this of course requires not allowing any file moving in the installation process unlike the pear installer. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
