Hm, this was the only topic I could find that even REMOTELY seemed appropriate for this question. It's kind of a doozy...<br /><br />I work at a contract development shop, and for the last year, have been working with a client who has been combining a number of different "Web 2.0" (*boo*hiss*) ideas. Well, we've seen success with the product, and now we're starting to license it out.<br /><br />Here's my predicament: I've been put in charge of "whiteboxing" the product, and getting it ready in some sort of tarball format. We only want SOME of the features to be included with the "base" package, and then we ask our licensee to pay more for certain features. The problem is, right now, the files that give those extra features are in our cvs development tree. For instance:<br /><br />classes/Foo/Bar.php<br />classes/Bar/Foo.php<br />widgets/Extras/<br /><br />I need to find a way to set up these files in a module manner, so that the base tree only has base functionality, but the module can be checked, so that Bar.php is installed in classes/Foo/ and the Extras folder is checked out in widgets/<br /><br />Does anyone here have experience with that? I'm kinda flying blind here. All the code base is PHP/Javascript, and all of these modules are PHP classes, etc. We've got it set up with config variables so the files aren't NEEDED to run the base stuff, so they can be safely removed, but we'd like to automate adding additional files from a module into the source tree.<br /><br />If I can't get this figured out, well, I'm gonna have to make one heck of a Makefile that will remove those files/folders unless otherwise specified.<br /><br />rockstar_
</div>
</div>