thomasbachem
Feature Request - composer
I'm working on this, but the problem is that I'm trying to avoid putting composer.json into the root of the repository, because it belongs in src/php/composer.json. That however doesn't seem to be possible with Composer.
I guess it's mandatory to have composer.json in the root. I don't see why it has to be in src/php/composer.json unless you want to make it cross-language which is not a common practice. Normally you will have each repository for specific language, more or less as a bundle which can be easily loaded with composer.
Anyway nice list, keep it updated :)
I just talked to seldaek from Composer, and he confirmed that this isn't possible indeed.
I think it makes no sense to have multiple repositories if the language libraries are mostly about 20-50 lines of code each – that would make things a lot more complicated. I prefer having them in src/[lang]/.
I'll decide on this soon ;).
I would like to build a JavaScript / node.js module, but I think we have the same problem there.
Have you thought about creating a GitHub organisation with one repository for the JSON file and n other repositories for the different implementations?
@sebbo2002 I thought about that, but I'm really not sure about it.
Another disadvantage would be the split attention/watchers/stares between the different repositories...
Another advantage would be, that every developer would be able to maintain his implementation (branches, tags, downloads, etc).
Yeah, but honestly, we're talking about code that will usually be around 20-100 lines. I'm not sure one needs fancy branches for that :D.
Having two repositories to make Webmail Linker work makes using it more complicated – we would need to use submodules for the config or the user needs to check out two repositories, which is also very uncommon. How would you do it?
I uploaded my prototype here. Before I create the tarball for npm I copy the latest JSON from your repository, so it's always bundled and can easily updated via npm/bower. New versions could be created automatically, when the JSON gets updated.
- easy installation process (for example
npm install webmail-linker) - update via packet manager (npm, bower or whatever)
+1 I'd love to install this repository via bower. I don't see a problem here. Every modern packet manager expects the configuration files in the root folder (bower, npm, composer).
https://github.com/MadaManu/angularjs-maillinker - the AngularJS flavour of this. Maybe we can integrate somehow at some point. I have registered this one on bower. I will update with documentation soon.
As a workaround you can add this to your composer.json to install webmail-linker via composer:
{
"type": "package",
"package": {
"name": "webmail-linker",
"version": "0.1",
"source": {
"url": "https://github.com/thomasbachem/webmail-linker",
"type": "git",
"reference": "origin/master"
}
}
},
