Posts

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 info@openhub.net

Technical Issue Help : Incorrect language accounting

The testers enlistment didn't suffer a major change: it is a new module, and when I first imported the code into its Git repository it was all C. The testers enlistment has never seen C++ code. So ... [More] , to summarize, the kyua enlistment suffered a significant refactor (dropped tons of C++ code, but added some more) and the testers enlistment appeared all afresh with brand-new C code. If you think a fresh reimport will help, please go ahead. (I'm not aware of what side-effects that will have, but I'm expecting none!) Thanks! [Less]

Views
Author
Posted
530
about 12 years ago

Suggestions for Ohloh 2.0 : Recognize includes from Automake files

Hello, In my projects, I always create a top-level Makefile.am that includes (with the include directive of Automake) files from other directories. (Why? I don't want recursive make.) These files ... [More] have the name Makefile.am.inc instead of Makefile.am, to prevent Automake from picking them up automatically. The problem is: the source scanner used by Ohloh doesn't seem to recognize these Makefile.am.inc source files and therefore does not count their lines towards the amount of Automake lines. Could you implement a fix for this issue? I'm not sure if the parser is intelligent enough to be able to determine the format of a file based on inclusions of it. For reference, one project affected by this is Kyua, which I just created in Ohloh. Thanks! [Less]

Views
Author
Posted
711
over 14 years ago

Technical Issue Help : NetBSD CVS enlistment stuck

Hello, The main enlistment for the NetBSD source tree, :pserver:anoncvs:anoncvs@anoncvs3.us.NetBSD.org:/cvsroot src, has been stuck for 5 months. AFAIK, it has actually never worked. This prevents ... [More] the NetBSD project in Ohloh to provide any kind of realistic information. Could you please take a look? Thanks. [Less]

Views
Author
Posted
483
over 14 years ago

Technical Issue Help : Problems with some enlistments

Aha, I see. Thanks for the explanation. I'm wondering... couldn't the failed enlistments be ignored so that they don't prevented all the others to work? By the way, about the NetBSD repository: I ... [More] don't know if this would be useful to you, but the whole repository (the CVS root on the server, not only a head checkout) is available through rsync. You'd use that to set up a local CVS root for NetBSD, just as you do with FreeBSD (or at least that's what I understood from some other post in the forums), which I guess could be much faster than using rlog. [Less]

Views
Author
Posted
898
almost 18 years ago

Feedback Forum : Reason for giving kudos

Cool! Great to hear that.

Views
Author
Posted
833
almost 18 years ago