[Bro-Dev] #435: topic/jsiwek/doc-framework

Bro Tracker bro at tracker.icir.org
Mon Apr 18 20:06:17 PDT 2011


#435: topic/jsiwek/doc-framework
---------------------+------------------------
  Reporter:  jsiwek  |      Owner:  jsiwek
      Type:  Task    |     Status:  assigned
  Priority:  Low     |  Milestone:  Bro1.6
 Component:  Bro     |    Version:  git/master
Resolution:          |   Keywords:
---------------------+------------------------

Comment (by robin):

 On Tue, Apr 19, 2011 at 01:04 -0000, you wrote:

 >  The master list of input sources is defined in
 `generate_reST_docs.py.in`.

 So, once we list everything there, these messages will go away? Then
 nevermind.

 >  I was struggling somewhat to come up with a good way to organize this
 >  process, so let me know if you had some other ideas on how/if I can
 >  improve it.

 Can't think of much else. Let's organize the scripts once the new ones
 for 1.6 are in place.

 >  I made it do a clean before each run because Sphinx was always adding
 new
 >  files in the `_downloads` output dir regardless of whether the policy
 >  script actually changes.  So I was ending up with `alarm.bro`,
 >  `alarm2.bro`, `alarm3.bro`...

 Could we delete just the _downloads directory but keep the state?

 Robin

-- 
Ticket URL: <http://tracker.icir.org/bro/ticket/435#comment:7>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker



More information about the bro-dev mailing list