With the latest release we’ve received quite a bit of feedback and one of the main things people have been saying is that they’d like the installation made easier (and/or better documented). We’re all too aware of the need to make it easy to get up and running quickly and we’ve have tried to simplify things as much as possible. One of the difficulties is that KForge intentionally focuses on reusing other tools extensively. This means there are quite a few dependency issues that can catch people out. One good suggestion we’ve had is to prepare a proper deb package for those on debian and ubuntu. One difficulty even with this is what we include. Some people just want subversion and trac, others just the wikis and wordpress. Do we just put everything in or do we ship a core version and leave it up to admins to install the extra plugins as and when they need them?

One Response to “Improving the Installation Process”

  1. Bongo Pongo King Says:

    i think that best is to create kforge-common deb package and module-like packages which will depend on it. Placing debian folder into src would be nice (so we can regenerate our packages from svn). I am looking forward to try this deb package :D

Leave a Reply