Autoloader cannot work as is

[composer]

Autoloader cannot work as is

[igorw]

For this reason we already do have a target-dir property that can be set. This is the same as the originally proposed "installAs". It allows you to specify where the package is installed.

For bundles:

{
    "name": "fos/rest-bundle",
    "type": "symfony-bundle",
    "target-dir": "FOS/RestBundle",
    "autoload": {
        "FOS\\RestBundle": "."
    }
}

This will install the package into vendor/bundles/FOS/RestBundle and set the autoloader to point to vendor/bundles.

For components:

{
    "name": "symfony/console",
    "target-dir": "symfony/src/Symfony/Component/Console",
    "autoload": {
        "Symfony\\Component\\Console": "symfony/src"
    }
}

Will install into vendor/symfony/src/Symfony/Component/Console and point the autoloader to vendor/symfony/src.

Basically, if a target-dir is provided, the target-dir is relative to the main install dir (like vendor or vendor/bundles), if none is provided, it's relative to where the package is installed (e.g. vendor/monolog/monolog).

[fabpot]

Thanks for the info.

But why things are installed relative to the main install dir when using target-dir? It's not consistent and I really like the fact that an installed library is always installed under its name. That way, no conflict is ever possible.

[igorw]

I don't really care where things are installed, I'd be fine with having everything strictly in package dirs. Ping @everzet.

[Seldaek]

Yeah I am with @fabpot on this one. I didn't care enough to spend hours arguing it back then, but I prefer complete isolation of packages as well.

As for supporting one namespace in multiple dirs. It is already possible, but I don't think it's necessary in this case? Do you have an example?