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]
incorrect language identification
clisp uses custom preprocessors for C, so it keeps the sources in *.d files which actually contain C code.
ohloh identifies then as written in d programming language
.
I suggest a custom per-project map identifying which files are in which labguage, similar to the existing cvs uid map. e.g., I should be able to specify that *.l in clocc is actually lisp and *.d in clisp is actually C.
another example is the *.tst (regression tests) files in clisp, which are actually lisp files.
I like this a lot. We've discussed similar approaches in the past, it might be time for us to re-evaluate.
A twist to add here is that if we allow file GLOB specifiers we could potentially overlap another highly-requested feature: ignoring directories.
Example directives:
/test/*.tst : LISP <-- treat as LISP
/doc/* : NULL <-- ignore all files in the doc directory
The challenge here is how could ohloh support this in a manageable way (not cause too much stress on servers, how to limit the possibly blooming support requests, etc..). We'll talk about it today and report back on our position ;-).
note another usage: ignoring generated files:
configure:NULL
I think generated files shouldn't be in source control anyway.
runs away before this becomes an argument
I think generated files shouldn't be in source control anyway.
let us not confuse normative and positive issues.