Organization

[nickcharlton]

Organization

[nickcharlton]

Thanks! It'll be nice to get some input on some of the decisions/compromises I made – I think we will run into some limitations of it being based around Rake.

Default Build

• Changing rake default to rake all seems like a good idea and I think a standalone rake should give us a list too.
  • (usually rake alone would fire off the test suite.)
• One of the problems with rake is that you can't pass arguments cleanly. You'd end up with something like:

rake build -- --distro=debian --type=chef

…and the implementation will be even worse than it is now. I'll think about it a bit.

Adding CentOS

• Yes, it assumes it's Debian-based at the moment.
• If we can, I'd prefer to keep it just as common/, but with fall-through blocks (like vmtools.sh) on options.
  • as long as it can be kept reasonably short.
• You're right about the lack of codenames. Renaming is probably the best approach; my other ideas seemed a little clunky.

---

I'm currently working on something to handle the subprocess (to Packer) better and interpret some of the output that flies by. I've noticed that if something goes wrong when doing a full build you find yourself scrolling and scrolling through the results.

So, forgive me if I don't merge many pull requests whilst I put this together, it looks like it'll change quite a bit of the Rakefile around.

[nickcharlton]

Closing this as it's been open a long time. I'm now working on some new (big) changes which I hope will address most, if not all of them.