Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
enlistments, complete source or only pure code excluding 3rd party libs etc?
Hi,
i just committed the lates version of tellmatic to cvs as an inital commit.
when its measured, it will include and count all codelines, also the 3rd party open source libs which are included in the package.
should i add an enlistment to the cvs repo and module containing the complete source?
or just a pure-code commit, containing no other opensource libs and tools i used with my application/script/whatever?
i tried both, first one included the whole commit, including all 3rd party libs etc. (>100k lines), the second enlistment (i deleted the first) points to a commit with almost only my own code then (23k lines).
how other people will do that ?
vizzy
ps: sorry for my broken english
Hi vizzy,
I think you should do whatever is best for your project -- whatever will be most convenient for developers.
If your main concern is the Ohloh report, I recommend that you only include your own code, and omit the 3rd party libs.
hi, thanks for the response.
i think i will measure the whole project including the 3rd party apps.
yes, the main concern would be the Ohloh report, but i don't know a good way to mainatin 2 cvs repositories/modules at once.
Every commit must be done twice, once for the pure-project coe, and one for the release containing the modules. thats a lot of extra stuff and time.
My suggestion to Ohloh to solve this 'problem' would be to have something like a 'included libs' section for the project - in short: dependencies.
E.g. if you have a project like tellmatic, which uses tinymce and some other libs which are listed in Ohloh, i would select which modules i use, e.g. tinymce, and the report will list the projects and do something like subtract this code from my enlistment.
Let me explain:
We have Project A containing 20k of lines, and Project B containing 5k lines of source.
Then a new Project C comes up which uses Project A and B as a library, the contributor of Project C select Project A+B as a 'connected' library Project C depends on.
So if Project C is measured with 35k lines of source, Ohloh will list Project A and B as a included library and will list these libs too.
Finally counting complete lines of code and subtract lines from Project A and B.
This would be a nice feature too, so we would have a cool overview what project/lib is used by another :)
The only thingy is that if you have e.g. Project A+B were counted with included examples, and Project C strips these examples files from the source, the Report will get confused.
Example: Project A+B contain e.g. 10k lines for example pages and Project C strips these files/lines from the source/enlistment, so that these lines of code will not exist in Project C, Project C would have a real line count of 35k minus Project A+B = 35K-25K = 10k lines of code, but in real it will use 10k more (total of 20k lines) because of the not included example files or lines of code...
I personally decided to include all files from a 3rd Party lib, including all sources and examples.
Only an idea,
greetings and thanks for this great service
vizzy