Add InstallerInstaller

[composer]

Add InstallerInstaller

[Seldaek]

@naderman: There is a little issue here ;) For custom installers to be registered during install, or at all for that matter, we need to know which class in the package to run, like:

  "extra": {
    "class": "Symfony\\Bridge\\Composer\\BundleInstaller",
    "file": "src/Symfony/Bridge/Composer/BundleInstaller.php"
  }

The file entry would also be helpful otherwise we need to parse the autoload config at runtime, and that could prove complex.

What this means though obviously is that this class can't have any dependency, it'll just get a vendor directory, the download manager and the local repository injected, and has to be able deal with that. I'm not sure this will be sufficient, but I guess it's the only way, if people need more they probably will have to wrap composer into their framework/app to provide custom logic.

[naderman]

Why can't we rely on the supplied auto loading information of that package? We don't have a generated autoloader yet, but we could register a very trivial PSR-0 autoloader based on the package contents right there and then?

[naderman]

And regarding dependencies, I think that's fine. It'll be ok for that kind of an installer to load custom code in its implementation and make use of that.

[Seldaek]

We can rely on the autoload info, it's just annoying to load that stuff inside the installer, we might need the "file" entry as optional anyway for packages that aren't autoloadable. Sounds reasonable?

[naderman]

Can't we require that installers are always auto loadable?

[naderman]

I'd just really like to keep our config options as minimal as possible.

[Seldaek]

Sure we can do that too. I hope I can look into it this week.