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

[Bro Tracker]

#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):

 >  But I also realized that's not the only thing holding back the ability
 to
 >  do incremental builds.

 Got it. Ok, no big deal, let's leave it as it is.

 >  1) Just change the link to point to the basename (bar) so that the link
 is
 >  fixed (the link text still says "foo/bar")
 >  2) Create directory trees for the Sphinx input sources that mimic how
 the
 >  scripts are `@load`ed.

 >  (1) should be easy, (2) seems more involved.  (1) seems ok if we don't
 >  expect to ever have multiple "bar" scripts that reside in different
 >  directories

 Per Seth's reply, would be good to support this. Is there a middle way
 of keeping the flat structure and just naming the files in some unique
 fashion (e.g., foo/bar -> foo_bar)? Don't know whether that makes
 sense.

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