--- 00TODO 2002/02/04 21:57:09 1.17
+++ 00TODO 2002/02/05 20:37:34 1.18
@@ -1,14 +1,5 @@
00TODO: Tasks left to accomplish before rc is complete
-!PROBLEMA!
-$ ./configure
-checking whether to build against external Dmalloc library... no
-checking whether to build against external OSSP popt library... no
-checking whether to build against external OSSP ex library... no
-checking whether to build against external OSSP Str library... no
-checking whether to build against external OSSP Var library... no
-configure: creating ./config.status
-
Unfinished business
Manpage options incorrectly specifies multiple rc.funcs.
What when multiple command interpreters and one --print or --eval given?
@@ -18,9 +9,11 @@
Give example semantics of a common scenario.
No error semantics in pseudocode.
+Document
+ Refs, pri, user, group, ci, go only in normal (not special) sections.
+
Consider
Removing the OSSP_RC_DEACT deactivation feature (thl.)
- Make return code and error definitions unique to OSSP rc.
Offer include directive in config file.
Dynamic handling of command interpreter option.
Environment of manpage has redundant text.
@@ -28,14 +21,10 @@
Als variable in %config Section?
Must do
- Strip local getopt and popt code, and use OSSP popt library.
- Translate rc bourne shell script to ANSI C.
+ Translate rc bourne shell script to ISO C.
Finish man page. Start latex or Docbook guide.
If a variable is defined for which no default exists, warn user (Scholli.)
-Document
- Refs, pri, user, group, ci, go only in normal (not special) sections.
-
Detailed ;-) project plan
-------------------------
Release v0.8
|
