[bind10-dev] Consistent way to define paths to socket files for all uses... or something...

[JINMEI Tatuya / 神明達哉]

At Fri, 13 Jul 2012 21:35:45 +0200,
Shane Kerr <shane at isc.org> wrote:

> I'm supposed to create a ticket based on our team call yesterday, but
> I'm not sure what is supposed to be in it!
> 
> If someone who was on the call can help me make sense of exactly what we
> need to do, I would be most grateful:

There are several places where this type of information is stored:
- src/lib/python/bind10_config.py
- in specific python scripts like xfrout.py
- in some C++ files like auth/common.{h,cc}

It's just a mess.  When you need to know the path, you'll need to
find multiple places.  When you need to add a new path, there can be
several ways and it's also possible that you invent yet another
place.  Also, there are some inconsistent cases like #1903.

So, what exactly I would envision is:

- introduce a unified place to define this information for all
  modules.  ideally this should be the only source for both Python and
  C++.
- Python scripts and C++ sources refer to this place and use the
  information appropriately.
- Document the policy and how you add new things to the unified place.

---
JINMEI, Tatuya