install packages via composer, update travis, updates in readme #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We will change the
shama/aura-system-installertoaura/system-installeror something or something like that and move the https://github.com/shama/aura-system-installer to our own repo.Thanks to the good work done by @shama to make this happen via the discussions happened at composer/installers#24
Thus we resolve all the Aura.Package related issues .
The current one is for Vendor.Package of others which are aura specific.
This is done as in https://github.com/harikt/Hari.Contact/blob/master/composer.json
That means we make mark
"type": "aura-package". But the only problem there is if that particular package is a library . We may want to find a solution for that ? Will it happen to be a library ? If so we will make it load viavendorfolder itself , but the config and stuffs , I am not sure .But I feel strong that the vendor packages other than
Auravendor which are aura specific will never become a library type .