* init.d-script-missing-lsb-section /etc/init.d/xorp

* postrm-does-not-call-updaterc.d-for-init.d-script /etc/init.d/xorp

* make manpages: xorp_rtrmgr, xorpsh

* Currently the logs generated by xorp_rtrmgr are lost as 
  start-stop-daemon closes the stdout/stderr descriptors and they
  cannot be redirected. How to solve this?

* User 'xorp' and group 'xorp' should be created:
   Xorpsh user guide just mandates that the user belong to group 'xorp'.
   (so root runnig 'xorpsh' and then 'configure' will not work)

* implement status check on init.d (xorp can die without a warning in syslog)

* init.d's restart does not work (xorp takes some time to tear down)

* daemon should logs messages by syslog, instead to specific files
  Temporary to help debug xorp and the packaging.  To be resolved when
  package is ready to be included in Debian.
  -->  [JFS] I think generation of logfiles at /var/log/xorp/ is better
       since xorp's output is very verbose and would flood syslog

* the generation of the docs need to be updated because of transition from
  tetex to texlive
  --> [JFS] Works for me fine in sid. What needs to be updated?

  --> [CAL] Finner depends on texlive, done.

* See (c) of the new files in source 1.5

* Run make tests on amd64 sid

* Run make tests on i386 sid

* Look into Release Notes 
   The new features not enabled on previous version are forced to be
   disabled.  The other, olsr, is left enabled as in previous version.

* check if OLSR is enabled?
  OLSR is an recent addition to xorp and is enabled be default
  A bug in configure.in disable it instead of enable using --with-olsr




* Check for what versions this patch "pim_register_ftbfs_linux_2.6.26"
   is needed

   Bug 767 on xorp.org

   The workaround was accepted in the upstream of xorp and was fixed
   in kernel release of 2.6.26.4.  So possibly kernels headers are
   broken from 2.6.26 until 2.6.26.3

* Check new options of xorp_rtrmgr on 1.6
   Are they sincronized with man page xorp_rtrmgr.8
   patch: xorp_rtrmgr.8_new_options

* Study autoconf and propose a fix for the bug related with olsr.

* Needs to find howto clean olsr build

* Consider adding a Build-Depends on snmpd so that Xorp's configure
  tests if dynamic linking will be possible (and thus, snmpd support
  makes sense)

* Make a proper patch to fix --with-snmp configure The tests used by
   configure are correct for a production machine where a snmpd daemon
   is running.  But not for a compilation machine.  Some tests need to
   be eliminated and replaced with information about snmpd daemon in
   Debian.

* Maybe the tests for snmpd are harmless, so snmpd can be a Build-Depend

* extra options proposed for snmp support on compiling machines

* Upgrade for Debian Policy 3.8.3

* Check if daemon mode works
  It works

   Bug 795 on xorp.org
   Bug 884 on xorp.org is restricted
   
   Currently the logs generated by xorp_rtrmgr are lost as
   start-stop-daemon closes the stdout/stderr descriptors and they
   cannot be redirected. How to solve this?

* Put back hack on configure to not test snmpd on build time

* Update debian/copyright
  
* It have a function for daemonize, see if is used and usefull
  maybe the daemon command from Debian is better

* Study the output of configure
   It is using iptables-dev?  I think xorp don't use it.
   Build-Conflict to be certain.

   Net-SNMP support is enabled? No is not enabled and so will stay
   that way until lenny is released.
