X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=TODO;h=0321768afc297d6500b6832aa50f1a054631765f;hb=ef6a361a079fbf03950cc405a1ce92c3447563ef;hp=191b2d45a34b0dcbc5ada80c93f96b66298b3cae;hpb=ca7c786f62c734ab4d4272dc9b842a3ac742f0ed;p=platform%2Fupstream%2Fcoreutils.git diff --git a/TODO b/TODO index 191b2d4..0321768 100644 --- a/TODO +++ b/TODO @@ -1,15 +1,48 @@ -comm: add an option, --output-delimiter=STR - Files to change: src/comm.c, ChangeLog, NEWS, doc/coreutils.texi, - Add a new file, tests/misc/comm (use another file in that directory as - a template), to exercise the new option. Suggestion from Dan Jacobson. +If you're interested in helping, here are some tasks that we've considered +over the years. Beware: some are quite old and no longer valid. To avoid +wasting your time by duplicating work or by working on a task that is no +longer pertinent, please search the mailing list and post your intent +before embarking on a big project. + +================================================== +Modify chmod so that it does not change an inode's st_ctime + when the selected operation would have no other effect. + First suggested by Hans Ecke in + http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/2920 + Discussed more recently on . + +document the following in coreutils.texi: + runcon + chcon + mktemp + [ + pinky +Also document the SELinux changes. + +Suggestion from Paul Eggert: + More generally, there's not that much use for imaxtostr nowadays, + since the inttypes module and newer versions of gettext allow things + like _("truncating %s at %" PRIdMAX " bytes") to work portably. + I suspect that (if someone cares to take the time) we can remove + all instances of imaxtostr and umaxtostr in coreutils and gnulib. + +cp --recursive: use fts and *at functions to perform directory traversals + in source and destination hierarchy rather than forming full file names. + The latter (current) approach fails unnecessarily when the names + become very long, and requires space and time that is quadratic in the + depth of the hierarchy. [Bo Borgerson is working on this] printf: Now that gnulib supports *printf("%a"), import one of the *printf-posix modules so that printf(1) will support %a even on platforms where the native *printf(3) is deficient. - Suggestion form Eric Blake. + Suggestion from Eric Blake. -strip: add an option to specify the program used to strip binaries. +renice: POSIX utility, needs implementing. + suggestion from Karl Berry (among others). + Bob Proulx is working on this. + +install: add an option to specify the program used to strip binaries. suggestion from Karl Berry doc/coreutils.texi: @@ -26,13 +59,6 @@ And once that's done, add an exclusion so that `cp --link' no longer incurs the overhead of saving src. dev/ino and dest. filename in the hash table. -See if we can be consistent about where --verbose sends its output: - These all send --verbose output to stdout: - head, tail, rm, cp, mv, ln, chmod, chown, chgrp, install, ln - These send it to stderr: - shred mkdir split - readlink is different - Write an autoconf test to work around build failure in HPUX's 64-bit mode. See notes in README -- and remove them once there's a work-around. @@ -48,15 +74,9 @@ printf: consider adapting builtins/printf.def from bash df: add `--total' option, suggested here http://bugs.debian.org/186007 -seq: give better diagnostics for invalid formats: - e.g. no or too many % directives -seq: consider allowing format string to contain no %-directives - tail: don't use xlseek; it *exits*. Instead, maybe use a macro and return nonzero. -add mktemp? Suggested by Nelson Beebe - tr: support nontrivial equivalence classes, e.g. [=e=] with LC_COLLATE=fr_FR lib/strftime.c: Since %N is the only format that we need but that @@ -89,26 +109,21 @@ sort: Investigate better sorting algorithms; see Knuth vol. 3. 5.3.1, who credits Lester Ford, Jr. and Selmer Johnson, American Mathematical Monthly 66 (1959), 387-389. -cp --recursive: perform dir traversals in source and dest hierarchy rather - than forming full file names. The latter (current) approach fails - unnecessarily when the names become very long. - Remove suspicious uses of alloca (ones that may allocate more than about 4k) Adapt these contribution guidelines for coreutils: http://sources.redhat.com/automake/contribute.html +Improve test coverage. + See HACKING for instructions on generating an html test coverage report. + Find a program that has poor coverage and improve. Changes expected to go in, someday. ====================================== dd patch from Olivier Delhomme - Andreas Gruenbacher's xattr changes - - Apply Bruno Haible's hostname changes - test/mv/*: clean up $other_partition_tmpdir in all cases ls: when both -l and --dereference-command-line-symlink-to-dir are @@ -117,18 +132,12 @@ Changes expected to go in, someday. an implicit --NO-dereference-command-line-symlink-to-dir meaning. Pointed out by Karl Berry. - A more efficient version of factor, and possibly one that - accepts inputs of size 2^64 and larger. - dd: consider adding an option to suppress `bytes/block read/written' output to stderr. Suggested here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=165045 Pending copyright papers: ------------------------ - ls --color: Ed Avis' patch to suppress escape sequences for - non-highlighted files - getpwnam from Bruce Korb pb (progress bar) from Miika Pekkarinen @@ -142,42 +151,36 @@ Add a distcheck-time test to ensure that every distributed file is either read-only(indicating generated) or is version-controlled and up to date. -Implement Ulrich Drepper's suggestion to use getgrouplist rather - than getugroups. This affects only `id', but makes a big difference - on systems with many users and/or groups, and makes id usable once - again on systems where access restrictions make getugroups fail. - But first we'll need a run-test (either in an autoconf macro or at - run time) to avoid the segfault bug in libc-2.3.2's getgrouplist. - In that case, we'd revert to using a new (to-be-written) getgrouplist - module that does most of what `id' already does. Or just avoid the - buggy use of getgrouplist by never passing it a buffer of length zero. - See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200327 - -remove `%s' notation: +remove `%s' notation (now that they're all gone, add a maint.mk sc_ + rule to ensure no new ones are added): grep -E "\`%.{,4}s'" src/*.c +remove all uses of the `register' keyword: Done. add a maint.mk rule + for this, too. + remove or adjust chown's --changes option, since it can't always do what it currently says it does. +Support arbitrary-precision arithmetic in those tools for which it +makes sense. Factor and expr already support this via libgmp. +The "test" program is covered via its string-based comparison of +integers. To be converted: seq. + Adapt tools like wc, tr, fmt, etc. (most of the textutils) to be multibyte aware. The problem is that I want to avoid duplicating significant blocks of logic, yet I also want to incur only minimal (preferably `no') cost when operating in single-byte mode. -Remove all uses of the `register' keyword - pr's use of nstrftime can make it malloc a very large (up to SIZE_MAX) buffer -ls.c: use gettime rather than clock_gettime, gettimeofday, time - ----- -Copyright (C) 2002-2007 Free Software Foundation, Inc. +Copyright (C) 2002-2008 Free Software Foundation, Inc. -This program is free software; you can redistribute it and/or modify +This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by -the Free Software Foundation; either version 2, or (at your option) -any later version. +the Free Software Foundation, either version 3 of the License, or +(at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of @@ -185,5 +188,4 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License -along with this program; if not, write to the Free Software Foundation, -Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. +along with this program. If not, see .