summaryrefslogtreecommitdiffstats
path: root/bin/ls/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* Use humanize_number(3).pjd2004-05-251-2/+2
| | | | Reminded by: jhb
* Get this area compiling with the highest WARNS= that it works with.markm2003-06-131-2/+0
| | | | | | | Obsolete WFORMAT= junk also removed where possible. OK'ed by: obrien Tested on: sparc64, alpha, i386
* Teach "ls -Z" to use the policy-agnostic MAC label interfaces ratherrwatson2002-10-241-1/+1
| | | | | | | | | | | than the LOMAC-specific interfaces for listing MAC labels. This permits ls to view MAC labels in a manner similar to getfmac, when ls is used with the -l argument. Next generation LOMAC will use the MAC Framework so should "just" work with this and other policies. Not the prettiest code in the world, but then, neither is ls(1). Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories
* Correct inadvertent style botches in previous commit.kris2002-02-041-2/+2
|
* Lock down with WFORMAT=1 except those directories with unfixed warnings.kris2002-02-041-0/+2
| | | | Tested on i386 and alpha.
* WARNS=4 fixes, plus a healthy dose of fixes inspired by lint.markm2002-02-031-1/+0
|
* Fixed style bug (unsorting of SRCS) in rev.1.15.bde2001-12-291-1/+1
|
* Fixed style bugs in revs. 1.6, 1.10 and 1.12.bde2001-12-291-3/+2
|
* Fixed missing DPADD and disordered LDADD in rev.1.17bde2001-12-291-1/+2
| | | | | | Fixed setting of WARNS in rev.1.16. Options should normally be set using using "?=", not using "=", so that the setting is easy to override on the command line, and setting WARNS to 0 should not be an exception.
* Add a new flag, -h which when combined with the -l option causesjoe2001-12-281-0/+1
| | | | | | | | file sizes to be displayed with unit suffixes; Byte, Kilobyte, Megabyte, Gigabyte, Terabyte and Petabyte in order to reduce the number of digits to three or less. Submitted by: nik
* Default to WARNS=2. Binary builds that cannot handle this must explicitlyobrien2001-12-041-0/+1
| | | | | | set WARNS=0. Reviewed by: mike
* Add LOMAC options (the "Z" flag in both cases) to display extra informationgreen2001-11-261-1/+1
| | | | | | in ls(1) and ps(1). Sponsored by: DARPA, NAI Labs
* Drop support for -DRELEASE_BUILD_FIXIT and -DCRUNCHED_BINARY inru2001-04-031-1/+1
| | | | ${CFLAGS}. The only supported method thus is -DRELEASE_CRUNCH.
* Switch over to using the new fflagstostr and strtofflags library calls.joe2000-06-171-2/+1
|
* Don't use ncurses, use termcapache2000-06-051-1/+2
| | | | Add DPADD
* Disable colour support in ls when building the fixit floppy, and makejoe2000-06-051-0/+2
| | | | a note of it in the release Makefile.
* * Re-implement colour support using termcap's AF and AB capabilitiesjoe2000-06-051-0/+3
| | | | | | | | | | | | | to manage the ANSI colour sequences. Colour support is disabled unless the TERM environment variable references a valid termcap. * Allow optional compilation of the colour support in the Makefile, defaulting to yes. This allows us to switch it off for fixit floppies and other mediums where space is an issue and the extra bloat of statically linking with ncurses isn't acceptable. * Display a warning if colour is requested with '-G' but support for it isn't compiled in.
* Revert part of the last commit, remove {g|s}etflags from the libcjoe2000-02-051-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | interface, and statically link them to the programs using them. These functions, upon reflection and discussion, are too generically named for a library interface with such specific functionality. Also the api that they use, whilst ok for private use, isn't good enough for a libc function. Additionally there were complications with the build/install-world process. It depends heavily upon xinstall, which got broken by the change in api, and caused bootstrap problems and general mayhem. There is work in progress to address future problems that may be caused by changes in install-chain tools, and better names for {g|s}etflags can be derived when some future program requires them. For now the code has been left in src/lib/libc/gen (it started off in src/bin/ls). It's important to provide library functions for manipulating file flag strings if we ever want this interface to be adopted outside of the source tree, but now isn't necessarily the right moment with 4.0-release just around the corner. Approved: jkh
* Historically file flags (schg, uschg, etc) have been converted fromjoe2000-01-271-2/+0
| | | | | | | | | | | | | | | | | string to u_long and back using two functions, flags_to_string and string_to_flags, which co-existed with 'ls'. As time has progressed more and more other tools have used these private functions to manipulate the file flags. Recently I moved these functions from /usr/src/bin/ls to libutil, but after some discussion with bde it's been decided that they really ought to go in libc. There are two already existing libc functions for manipulating file modes: setmode and getmode. In keeping with these flags_to_string has been renamed getflags and string_to_flags to setflags. The manual page could probably be improved upon ;)
* Added missing DPADD's. Removed unrequired SRCS's.joe2000-01-011-0/+1
| | | | Obtained from: bde
* Moved flags_to_string and string_to_flags into libutil. It's used injoe1999-12-301-1/+3
| | | | many places nowadays.
* $Id$ -> $FreeBSD$peter1999-08-271-1/+1
|
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* Added $Id$dg1994-09-241-0/+1
|
* BSD 4.4 Lite bin Sourcesrgrimes1994-05-261-0/+6
OpenPOWER on IntegriCloud