ok, i'm not being too crazy. I just tried this, and overwrote my config file with make.
Just think about devs: 1.) checkout from bzr 2.) hack on /src/WHATEVER 3.) commit -m "some message" WHATEVER 4.) make That is assuming you have your web server pointed to whatever you just built like aiki-0.7.0 folder. Really need to think this through, since I strongly prefer running websites from repo code...makes things easier for making commits. -- 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 : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
