install of "connect20/mage_all_latest": "1.7.0.2" about composer-repository HOT 7 CLOSED

I think this is because of the cutoff we apply to module age.
We need to include a few special rules for these Core packages into the build scripts. @thebod
This would be a quick subtask for the next hackathon maybe.

from composer-repository.

I worked around this by cloning those three packages and adding them to the repository definitions in my composer.json: https://gist.github.com/steverice/5874745

Definitely not the prettiest solution but it allows me to install CE 1.7.0.2 via composer without issues.

from composer-repository.

To get installation of Magento fully working with the composer installer, I needed a fix for links in the root directory:
steverice/magento-composer-installer@dec4886

I also needed to use "magento-deploystrategy":"link" to create hardlinks instead of symlinks as the Varien autoloader chokes when it discovers that none of the files it's looking for are in the same original vendor directory as itself. I imagine "magento-deploystrategy":"copy" would work as well. Maybe there's a better way to do this — perhaps being able to use the link or copy strategy only for the connect20/lib_varien package?

It seems some packages also like to clobber each other's packages, meaning I had to add "magento-force":true as well. Will update if I notice any ill effects.

from composer-repository.

the problem reported from me in the first place seems to be fixed, composer install works fine and files seem to be in place.

But I can approve the problems steverice describes. There is some functionality which works relative to the current file and is broken if used together with symlink deploy

from composer-repository.

have to correct my last comment.

there are still three unresolved dependencies. Did not notice them, because I had a replacement in my composer.json

the same as steverice named.

Will look if I can add them to our repository

from composer-repository.

have now added a workaround for the three missing packages.

I wrote a script which downloads the current version, repairs the tgz and stores it in our git repository.
Also I added them to the satis.json, so after next rebuild they are available.(and they are availabil and it works 😃 )

Future versions should not produce a defect tgz on connect, so they should work in future without this workaround.

the deploy strategy problem should get moved to an own issue, if someone thinks this will be a serious problem.

from composer-repository.

Closed, fixed with @Flyingmana repaired archives and a repaired lib_zf_locale 1.11.1.0 package.

from composer-repository.