BIND 10 #2899: move interprocess_sync under lib/log or make it a separate private lib
BIND 10 Development
do-not-reply at isc.org
Thu May 9 12:45:29 UTC 2013
#2899: move interprocess_sync under lib/log or make it a separate private lib
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: defect | jinmei
Priority: medium | Status:
Component: build system | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-20130514
Sub-Project: Core | Resolution:
Estimated Difficulty: 3 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => jinmei
Comment:
Hello
I couldn't run the tests, since it seems to be based on broken master (for
some reason, I get a bunch of failures from statistics tests). Even
merging with today's master doesn't help. I believe we should confirm
distcheck before merging this, as it creates new library and that's often
source of problems.
Also, with this text, isn't the reason why we don't use the boost
interprocess that it didn't work on some of our systems? Or it needed
compiled boost libraries?
And, should it use isc::log::interprocess instead of isc::log::internal? I
generally expect the library name and directory name and the namespace
match (with some mapping of lower/upper case, dashes and such).
As for the length because of file moves, I discovered that the `-M` switch
of `git diff` is quite useful.
--
Ticket URL: <http://bind10.isc.org/ticket/2899#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list