X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=doc%2FTODO;h=cd2721f6bee0efb94047fc4fef7ecdf7a8c3c63b;hb=78d072a8d942283723d94fbfb8f40e61d1f7fbe4;hp=f0d31c875a5ef15a82fcd2902b01f19fd1aa53d2;hpb=ff1eda3dfb95162cd26600ccdcc234d70916e1b8;p=debhelper.git

diff --git a/doc/TODO b/doc/TODO
index f0d31c8..cd2721f 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,62 +1,34 @@
-This is the TODO for debhelper. As more and more people use debhelper, this
-list grows - I welcome patches to fix items on it!
+v10:
 
-Wishlist items:
-
-* All debhelper programs should only accept the options they are documented
-  to accept (rather than accepting all debhelper options). They should
-  be able to print breif usage summaries.
-
-  I think this calls for a restucturing. Make a Debhelper.pm class. Each
-  program subclasses the class. The class provides command line parsing,
-  useful functions, and so on. Skeleton of a debhelper command would then
-  be:
-
-  use base qw{Debhelper};
-
-  sub startup {
-  	# Add initialization stuff here.
-  }
-
-  sub perpackage {
-  	my $package=shift;
-
-  	# Stuff to do for each package here.
-  }
-
-  sub fini {
-  	# And final stuff here, if any.
-  }
-
-  This needs more thought.
-  
-* Support use of environment variables in data taken from user, ie, in
-  debian/dirs. The problem with doing this is that we really want to allow
-  any filenames in that input, even those that look like environment
-  variables. However, it may be worth adding a switch to make it parse
-  environment variables. (#20964)
-* It's possible to speed up debhelper by having it cache some values that
-  multiple commands call. One way to do this would be to write dh_cache,
-  that generates the cache. The catch is that if the user runs that program,
-  they are stating that they don't do anything later to invalidate the cache,
-  without calling dh_cache again. (#23792)
-* Add a switch to dh_installdeb to allow it to do user defined
-  substitutions. OTOH, maybe it's better if people just sed
-  postinst.in before debhelper gets its hands on it... (#25235)
-* install-info, as of dpkg 1.10, parses the info file for section if
-  --section is not given. So I should be able to stop parsing it myself for
-  section, after dpkg 1.10 has been around long enough.
+* escaping in config files (for whitespace)?
+* dh_installinit --restart-after-upgrade as default?
 
 Deprecated:
 
-* DH_COMPAT 1. Can be removed once all packages are seen to be using 2 or
-  higher. I won't hold my breath.
-* Also, grep the entire archive for all dh_* command lines (I do this now),
-  and check to see what other switches are not being used, and maybe remove
-  some of them. I'd also like to depercate/remove debian/compress files, -X is
-  a better idea.
+* make a missing debian/compat an error. (started printing warning messages
+  in 20120115)
+* DH_COMPAT 1, 2, 3, 4. Can be removed once all packages are seen to be using
+  a newer version. I won't hold my breath. (2 and 3 are getting close though.)
 * dh_suidregister. Once nothing in the archive uses it.
-* dh_installmanpages. Only mildly deprecated right now. Once dh_installman
-  catches on, make it emit a warning, and then wait for it to go away.
-* dh_testversion. Remove as soon as nothing uses it.
-* dh_movefiles. I won't hold my breath.
+* dh_installmanpages.
+* dh_movefiles. I won't hold my breath. Have not added deprecation
+  docs or message yet.
+* dh_undocumented
+* dh_installinit --init-script (make it warn)
+* dh_python
+* dh_clean -k
+* dh_desktop, dh_scrollkeeper. Remove eventually..
+* -s flag, not formally deprecated yet; remove eventually
+* -u flag; add a warning on use and remove eventually
+* delsubstvar() and the last parameter to addsubstvar that makes it remove
+  a string are not used in debhelper itself, but have been left in the
+  library in case other things use them. Deprecate and remove.
+* dh --before , --after , --until , --remaining
+* debian/compress files
+* deprecate dh_gconf for dh_installgsettings (stuff should be migrating
+  away from gconf, and then I can just remove it -- have not added warning
+  or depreaction docs yet)
+
+Also, grep the entire archive for all dh_* command lines,
+and check to see what other switches are not being used, and maybe remove
+some of them.