| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
for a lot of unrelated error conditions, at least report the line
number where it bailed.
Don't use multiline string literals for Usage, gcc 3.3 doesn't like them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FreeBSD. This method attempts to centralize all the necessary hacks
or work arounds in one of two places in the tree (src/Makefile.inc1
and src/tools/build). We build a small compatibility library
(libbuild.a) as well as selectively installing necessary include
files. We then include this directory when building host binaries.
This removes all the past release compatibilty hacks from various
places in the tree. We still build on tip of stable and current. I
will work with those that want to support more, although I anticipate
it will just work.
Many thanks to ru@, obrien@ and jhb@ for providing valuable input at
various stage of implementation, as well as for working together to
positively effect a change for the better.
|
|
|
|
| |
Approved by: re
|
|
|
|
|
|
|
|
| |
unlink (very likely EPERM), since the errno from the open might
be a confusing ETXTBSY.
Approved by: re
MFC After: 1 week
|
|
|
|
|
|
| |
<sys/stat.h> for the declaration of struct timeval.
Approved by: re (rwatson)
|
|
|
|
|
|
|
|
|
| |
the deprecated utime(3). utimes(2) uses timeval, but utime(3) uses
time_t's. If you do bad things (like I did) by mixing up include files
with libc, then install can do strange things if you mismatch the time_t
stuff. utime() is emulated entirely within libc.
Approved by: re (jhb)
|
| |
|
|
|
|
| |
Document that -p also preserves the access time of the source.
|
|
|
|
|
|
| |
specified, the target file already exists and the files are
the same, and the target's file flags and mode need not to
be changed.
|
|
|
|
|
|
|
|
|
| |
Add some constness to avoid some warnings.
Remove use register keyword.
Deal with missing/unneeded extern/prototypes.
Some minor type changes/casts to avoid warnings.
Reviewed by: md5
|
|
|
|
|
|
|
| |
option. Warn about COPY being phased out. Restore the old method
of always comparing before installing: INSTALL="install -C".
Requested by: bde
|
|
|
|
|
|
| |
as was promised in revision 1.43.
MFC after: 1 month
|
| |
|
|
|
|
|
|
| |
PR: 30543
Approved by: dwmalone (mentor)
MFC after: 3 weeks
|
| |
|
| |
|
|
|
|
|
|
| |
environment variable that specifies the name of the strip(1)
program to use. The envvar is "STRIPBIN". The more natural
choice would be "STRIP", but that one is taken already.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Do the usualy ifdef trick here.
Reported by: dworkin muller <addr-removed> and faried nawaz <fn@hungry.com>
|
| |
|
|
|
|
| |
during the bootstrap phase.
|
|
|
|
| |
PR: 31415
|
| |
|
|
|
|
| |
Spotted by: bde
|
|
|
|
| |
Idea from: Theo de Raadt <deraadt@openbsd.org>
|
|
|
|
|
|
| |
Also, fix markup in the SYNOPSIS.
Submitted by: dougb
|
|
|
|
|
|
|
| |
Instead, issue a warning for now if -d and -C options are used
together. This will be turned into an error before 4.5-RELEASE.
Reviewed by: imp
|
|
|
|
|
| |
"install -C" then things will fail due to new checks. Relax the
checks so that install -C -d works again.
|
|
|
|
|
|
|
|
|
|
|
| |
o New flags: -b and -B (backup)
o New flag: -S (safe copy; aka "atomic" install)
o The -c flag is now the default.
o The -D flag was withdrawn.
Reviewed by: bde (up to some point)
Obtained from: OpenBSD but heavily modified
MFC after: 1 month
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
A garbage timestamp was used for at least installing /dev/null with -C -p
when the target doesn't already exist.
|
| |
|
| |
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 ;)
|
| |
|
|
|
|
| |
Obtained from: bde
|
|
|
|
| |
many places nowadays.
|
| |
|
| |
|
|
|
|
| |
Submitted by: nrahlstr
|