summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorDan Bode <dan@bodepd.com>2010-03-16 07:42:46 -0500
committerDan Bode <dan@bodepd.com>2010-03-16 07:42:46 -0500
commite825530c106f9206e043a5c20010b6c5f3299892 (patch)
tree37106481acaca4663f705aed94480678d34596b5 /README
parentbe8a6c993c08433176aaf6341c6e5bb76b7b7bc3 (diff)
minor edits to the README
Diffstat (limited to 'README')
-rw-r--r--README8
1 files changed, 4 insertions, 4 deletions
diff --git a/README b/README
index 949e275..66c8c67 100644
--- a/README
+++ b/README
@@ -5,16 +5,16 @@ Examples of usage can be found in the tests directory. The type also has rdocs.
Sudoers supports ensure => (present|absent)
-*TODO(stuff that I hope to fix)
+*TODO(stuff that I will fix soon)
- 1. I can probably set up autorequires on aliases in User Spec line, but this order would only be followed if both records were created.
+ 1. Setting up autorequires for existing aliases, but this order would only be followed if both records were created.
2. A record (as determined by NAMEVAR) cannot switch between types. Currently throws an exception.
- 3 Can't log flush or to_line events because they occur too often (working on this per issue with parsedfile).
+ 3 Shouldn't log flush or to_line events because they occur too often (working on this per issue with parsedfile).
LIMITATIONS (things I will not fix soon):
1. No support for parsing multi-line files (with \). I may add this in the next revision.
2. Forced to use comments to specify NAMEVAR for user specs. This means that there is no
way to determine if an added line is the same as an existing line.
- 3. Dependencies are only aplied between records at creation time. It is not possible to insert a new record before an existing one. There is probably a good way to fix this, but I need more time to look into it. Currently discussing with dev, this may require a feature request in parsedfile??
+ 3. Dependencies are only applied between records at creation time. It is not possible to insert a new record before an existing one. There is probably a good way to fix this, but I need more time to look into it. Currently discussing with dev, this may require a feature request in parsedfile??
4. Performance issue with parsedfile- seems to be runing to_line way too many times, also flushing way too often