Maybe it's a bit early to be talking about this, but I've just run into
some problems with my local project starter (the thing I made for use in
some in-house projects at Plus Three by extracting stuff from Krang) and
I'd like to plan ahead for avoiding them with Matchstick.
The big issue is that my project starter is based on Krang from about 8
months ago. I keep running into various things that have been fixed in
Krang's build process (FC2 directory stuff, skipping .svn directories in
platform/, etc.) but have not been fixed in mine. Then I have to do a
manual merge to get each fix.
I would like it to be possible to easily upgrade the version of
Matchstick that your are using to distribute your code to the latest
release. One idea I had for this is to keep all of the Matchstick stuff
under one directory, so that you can just replace it with the latest.
I'm not certain how well we can isolate things though. Another idea was
to make a script for Matchstick that turns a project matching a given
file layout structure into a Matchstick distribution, so that you can
keep your project source totally separate and have Matchstick merge with
it after you check it out.
This also illustrates my problem with code generation schemes...
Get latest updates about Open Source Projects, Conferences and News.