Production build not recognizing package names, therefore 404's...

I'm trying to deploy to production and getting 404's on all resources of all packages.

Here's an example, a package called "customcss"

The package.json of it:

Code:

{
    "name": "customcss",
    "type": "code",
    "creator": "anonymous",
    "summary": "Short summary",
    "detailedDescription": "Long description of package",
    "version": "1.0.0",
    "compatVersion": "1.0.0",
    "format": "1",
    "local": true,
    "requires": [],
     "css": [{"path":"resources/css/custom.css","type":"css"}]
}

And what I end up seeing in the directory MyApp\build\production\MyApp\resources is directories for each packages with their proper resources in them, but the built application wants to look at http://site/resources/css/custom.css and not http://site/resources/customcss/css/custom.css which is what I'm expecting it to do.

Am I right in thinking this is what it should do ?

I run: sencha app build production