Oscap source

I agree that oscap_source could go to the common. The decision to make it separate was made, when the final design was not that apparent.

That being said, I still see a value in keeping oscap_source in separate directory. I think of the source/ or common/ directory as a module of kind. There are certain merits of having modules small. And there are merits in keeping dependencies minimized between modules. I believe these particular modules (source vs common) separated goes along these lines.

There is nothing requiring oscap_source from commons (except for obsoleted functions). Next, oscap_source hides some gears from other modules. Note that functions within oscap_source are used by other modules only when working with oscap_source.

The source module is very focused on one topic, that is: actions you can make with oscap_source structure. Where the common module is very universal. The functions in oscap_source follow very much the same theme. That can hardly be said about the common. I moved things from common to source, when I wanted to make sure that the given functions is used only by oscap_source. This process helped me to decouple some of the stuff.

Further, I could write whole oscap_source module to a single file. But I decided that I want to separate it to as many files as feasible. If I created another big file in common directory I wouldn't be improving the world that much.

That being said, I would really like to keep oscap_source is separate directory. I can move oscap_source to common/source, if you insist.