First off, the build system is not broken and this is not a bug, but possibly feature removal or addition. I can remove the build system. I don't have any reservations about it. However, that will definitely impact the automated releases and any files that are generated or modified from the build process.
Secondly it's my strong recommendation that when developing the code, a sequential process should be used similar to the following: 1. Check-out or Update a local source tree 2. Make a change to the local source tree 3. Build release from the modified local source tree 4. Install the newly built release 5. Run the newly installed release 6. If new release behaves as expected then commit/push modified local source tree. Otherwise, repeat steps 2 through 6 inclusive. Depending on what was changed, step 3 may be omitted and simple re-installation may be sufficient. Obviously, there are different ways to do this. However, that is what I do and recommend. Here's one reason why I do this. The releases that are being installed by any user/developer are what should be tested. Testing code that is from your local development sandbox doesn't validate that the released product is not broken. For example, changes made to the installer or SQL structures that create bugs can easily go unnoticed unless a clean re-installation of a release is done. -- You received this bug notification because you are a member of Aiki Framework Admins, which is subscribed to aikiframework. https://bugs.launchpad.net/bugs/689956 Title: build system broken for active aiki development Status in Aiki Framework: Confirmed Bug description: Build systems are awesome, but when they essentially make development impossible, we have problems. Right now, if you checkout from the main branch of aiki, you have to run ./autogen.sh && ./configure && make This then gives you the necessary build like aiki-0.7.0. ITs great! That we can generate packages, but, the problem with this is that the .bzr folders are removed from the code, and its not simple to type: bzr commit . inside of the aiki folder. Fosdevel, can you come up with a solution so we can just point our web server towards the /src folder in the checked out aiki branch so we can keep hacking. Right now, you have to build too much stuff to get a workable aiki installation, and essentially, that won't allow us to easily use bazaar. If I've overlooked something let me know. But, right now I consider this super critical because we are all busy and lazy, and need a simple solution to be able to commit fixes to aiki. Thanks! _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : aikiframework.admins@lists.launchpad.net Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
