MidCOM 3 packaging and distribution
Posted on 2008-06-27 09:36:58 EEST.
MidCOM 3 is progressing nicely. Few more this kind of sprints and we can hit beta.
Currently the biggest question is the Package management of MidCOM 3. PEAR has it's weaknesses especially if you want to have multiple installations and want to use real packages with them.
Yesterday we talked about the possibilities of git while having a beer. It seems that git should provide a quite good solution to the matter. We just need a list of packages and repositories and a list of dependencies. Rest is just git pull / cloning things.
The real candy in this solution is that you can use you developing environment as a source for your production server's git updates. You can first test new packages and functionality on dev servers. Do changes and local commit and after that update your production server.
This requires some work before that. The Roadmap of MidCOM 3 is available at git-repository. We try to move that to the midgard-project.org's trac soon.
Currently the biggest question is the Package management of MidCOM 3. PEAR has it's weaknesses especially if you want to have multiple installations and want to use real packages with them.
Yesterday we talked about the possibilities of git while having a beer. It seems that git should provide a quite good solution to the matter. We just need a list of packages and repositories and a list of dependencies. Rest is just git pull / cloning things.
The real candy in this solution is that you can use you developing environment as a source for your production server's git updates. You can first test new packages and functionality on dev servers. Do changes and local commit and after that update your production server.
This requires some work before that. The Roadmap of MidCOM 3 is available at git-repository. We try to move that to the midgard-project.org's trac soon.