Hi everybody, one of the core concepts of Symfony philosohpy is learn from the best around in different worlds (Perl, Python, Java) and make it better in PHP. I don't know how the SymfonyBundler project is getting along and I haven't had time to dive in the code, I thought I'd briefly mention a tool from the Drupal community called drush (DRUpal for SHell). One of its extensions is called drush make and lets developers define in a make file a set of bundles (modules in Drupal terminology) to be downloaded. Options are given to download tarballs, checkout from git/ svn. I think one of the coolest thing is being able to define a download plus a set of patches to apply.
Since I have never used any other package manager, what seems great to me might look pathetic or simplistic to someone more accustomed to better tools. I am curious to learn about what's the best around and what can be done better! Here are some links: http://drupal.org/project/drush_make http://drupalcode.org/project/drush_make.git/blob_plain/refs/heads/6.x-2.x:/EXAMPLE.make Cheers, Francesco -- francesco levorato aka flevour http://flevour.net/ - Follow me on Twitter here: http://twitter.com/flevour "Now while the blood is hot you should make your way with vigour to better things." (Seneca) On Mar 8, 3:56 pm, Lukas Kahwe Smith <[email protected]> wrote: > 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 athttp://symfonybundles.github.com/#Bundlerfor 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
