Open Sourcing with (Imperfect) Revision History?

Posted by Cliff on Saturday January 14, 2006 @03:45PM from the missing-dependencies-frustrate-compilers dept.

AArnott asks: "My company is open-sourcing a private project that has been in development for 4 years. It's history is all in our internal Subversion server. The history of the project includes dependencies on source code that we are not open-sourcing. Should we just publish the latest version (now that we've removed the dependencies) and leave out the old history? Or should we publish the history, even though no previous revision will build, due to the dependencies that we are not including?"

1 of 27 comments (clear)

Min score:

Reason:

Sort:

WTF? by XBL · 2006-01-14 15:55 · Score: -1, Troll

This has to be one of the dumbest Ask Slashdots ever posted.

Why release a version of your software's code that is useless to everyone outside of your organization? Just to confuse people who end up downloading your code? Just post the newest code without the dependencies. Duh!

BTW, thanks for making your code open source. I hope the code is a lot better than this question.