BIND 10 #2687: src/lib/python/isc/log_messages/work/__init__.py in tarball

[BIND 10 Development]

#2687: src/lib/python/isc/log_messages/work/__init__.py in tarball
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  task          |  UnAssigned
            Priority:  low           |                       Status:  new
           Component:  build system  |                    Milestone:
            Keywords:                |  Previous-Sprint-Proposed
           Sensitive:  0             |                   Resolution:
         Sub-Project:  Core          |                 CVSS Scoring:
Estimated Difficulty:  0             |              Defect Severity:  Low
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Description changed by jreed:

Old description:

> What is purpose of src/lib/python/isc/log_messages/work/__init__.py in
> the distributed tarball?
>
> I received an off-list email about issue that the file is included but a
> "distclean" removes it. It is inconsistent.
>
> Can someone explain src/lib/python/isc/log_messages/work/Makefile.am ?
>
> It has python_PYTHON set, so this is added to DIST_COMMON (becomes part
> of tarball).  I am guessing it should not use python_PYTHON. Anyways a
> ./configure generates it so shouldn't be in the tarball.
>
> But distclean removes it (is part of CONFIG_CLEAN_FILES).

New description:

 What is purpose of {{{src/lib/python/isc/log_messages/work/__init__.py}}}
 in  the distributed tarball?

 I received an off-list email about issue that the file is included but a
 "distclean" removes it. It is inconsistent.

 Can someone explain src/lib/python/isc/log_messages/work/Makefile.am ?

 It has python_PYTHON set, so this is added to DIST_COMMON (becomes part of
 tarball).  I am guessing it should not use python_PYTHON. Anyways a
 ./configure generates it so shouldn't be in the tarball.

 But distclean removes it (is part of CONFIG_CLEAN_FILES).

--

-- 
Ticket URL: <http://bind10.isc.org/ticket/2687#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development