auraphp/system — pull request #19 by harikt (2012-08-05 09:38:04+00:00)
Title: install packages via composer, update travis, updates in readme

We will change the `shama/aura-system-installer` to `aura/system-installer` or 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 https://github.com/composer/installers/issues/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

{
"name": "hari/contact",
"minimum-stability": "dev",
"type": "aura-package",
"description": "This is a sample contact page",
"keywords": [
"aura",
"sample"
],
"homepage": "http://harikt.com",
"time": "2012-07-30",
"license": "BSD",
"authors": [
{
"name": "Hari.Contact Contributors",
"homepage": "https://github.com/harikt/Hari.Contact/contributors"
},
{
"name": "Hari KT",
"email": "kthari85@gmail.com",
"homepage": "http://harikt.com"
}
],
"require": {
"php": ">=5.4.0",
"composer/installers": "*"
}
}

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 via `vendor` folder itself , but the config and stuffs , I am not sure .

But I feel strong that the vendor packages other than `Aura` vendor which are aura specific will never become a library type .