freebsd-nq/bin/rm/Makefile

#	@(#)Makefile	8.1 (Berkeley) 5/31/93
# $FreeBSD$

PROG=	rm
SRCS=	rm.c setflags.c

LINKS=	${BINDIR}/rm ${BINDIR}/unlink
MLINKS=	rm.1 unlink.1
.PATH:	${.CURDIR}/../../lib/libc/gen

.include <bsd.prog.mk>
BSD 4.4 Lite bin Sources 1994-05-26 06:18:55 +00:00			`# @(#)Makefile 8.1 (Berkeley) 5/31/93`
$Id$ -> $FreeBSD$ 1999-08-27 23:15:48 +00:00			`# $FreeBSD$`
BSD 4.4 Lite bin Sources 1994-05-26 06:18:55 +00:00
			`PROG= rm`
Revert part of the last commit, remove {g\|s}etflags from the libc 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 2000-02-05 18:42:36 +00:00			`SRCS= rm.c setflags.c`
Allow root to delete uchg/uappnd files 1995-04-13 13:35:09 +00:00
Add link(1) and unlink(1) as special cases of ln(1) and rm(1) respectively, in accordance with SUSv2. This differs from the approach taken in NetBSD, but provides less obscure error messages in at least the EISDIR case and does not take up additional disk space for new binaries. PR: 13071 PR: 13074 Requested by: James Howard <howardjp@wam.umd.edu> 1999-12-20 16:13:47 +00:00			`LINKS= ${BINDIR}/rm ${BINDIR}/unlink`
			`MLINKS= rm.1 unlink.1`
Revert part of the last commit, remove {g\|s}etflags from the libc 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 2000-02-05 18:42:36 +00:00			`.PATH: ${.CURDIR}/../../lib/libc/gen`
Add link(1) and unlink(1) as special cases of ln(1) and rm(1) respectively, in accordance with SUSv2. This differs from the approach taken in NetBSD, but provides less obscure error messages in at least the EISDIR case and does not take up additional disk space for new binaries. PR: 13071 PR: 13074 Requested by: James Howard <howardjp@wam.umd.edu> 1999-12-20 16:13:47 +00:00
BSD 4.4 Lite bin Sources 1994-05-26 06:18:55 +00:00			`.include <bsd.prog.mk>`