Actually you can make distribution package and install it like in wordpress with two glitches which I post to the list earlier.
But I agree with Jon, why we need this Makefiles shit, if we don't compile anything it's just php and JavaScript files, and installer.php do everything what "make install" do. We can simply make a distribution package, when it will be working (right now it don't copy codemirror and plupload) and then replace all source in Bazaar with content of that package. Or we can move files by hand, it will be easier because we won't be needed to fix Makefiles. We can keep one Makefile with "make dist" and maybe "make install", but I don't think we need this second one, and "make dist" can create a package outside the source like when you build deb package. On Fri, 23 Dec 2011 18:35:13 +0200 Bassel Safadi <bassel.saf...@gmail.com> wrote: > I agree, and that's exactly why I think we should focus on the web > installer much more than the make files which only few people know > how to use. > can you add those to a blueprint? I want the web installer to be super > easy, and currently it's not because of the make files that has to > move files and do stuff which breaks the web installer > > -- > Bassel Safadi | http://bassel.ws > Skype: i.know.sy | Global: +1-323-545-3855 > > > On Mon, Dec 19, 2011 at 2:10 AM, Jon Phillips <j...@fabricatorz.com> > wrote: > > > It just struck me that the course of aiki package development is > > wrong. > > > > What I'm thinking is we should totally make sure that the trunk of > > aiki framework is droppable on any web root and immediately show the > > web installer, much like wordpress works. > > > > Longer term, I would even like it if we had customizations to an > > aiki framework package, so it could be dropped even inside a web > > browser or a folder, and work with html5 and the limited sql > > support in the browser. > > > > What do you guys think? > > > > I've become concerned with how we are currently following the path > > of free software too much and making it too hard to develop on the > > system. > > > > I want to remove as many barriers as possible to both using and > > developing on aiki framework. > > > > If we are in agreement, then I think we should take a hacksaw and > > remove most of the root of aikiframework and bring /src to be the > > live site. > > > > We will then have to work out more about what gets replaced in the > > config, but think this is a better direction than adding more > > makefiles, and weird stuff that only nerds in free software > > understand. > > > > "Who cares" is what I'm thinking about if we get a web package into > > a free software distribution if aiki is a pain in the ass to deploy > > and develop. > > > > We need to learn from the simplicity of wordpress, and focus on some > > longer term goal. > > > > For me, I would love ot see aiki turn into a model citizen as the > > best way to development local and remote html5 apps. > > > > Jon > > > > -- > > Jon Phillips 王✳爻气 http://fabricatorz.com ✳ skype: kidproto ✳ > > irc: rejon +1.415.830.3884 (global) ✳ +86-187-1003-9974 (beijing) > > _______________________________________________ > > Discuss mailing list > > disc...@lists.fabricatorz.com > > http://lists.fabricatorz.com/listinfo/discuss > > -- Jakub Jankiewicz twitter: @jcubic www: http://jcubic.pl _______________________________________________ Mailing list: https://launchpad.net/~aikiframework-devel Post to : aikiframework-devel@lists.launchpad.net Unsubscribe : https://launchpad.net/~aikiframework-devel More help : https://help.launchpad.net/ListHelp
