| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Reviewed by:
Submitted by:
|
| |
|
|
|
|
| |
manual page for the com driver (which is no longer in our source tree).
|
| |
|
| |
|
|
|
|
|
| |
Reviewed by:
Submitted by: guido
|
|
|
|
|
| |
get built every time.
- Use the standard clean and cleandir targets.
|
|
|
|
|
| |
can elect to dump all finished packages in one directory).
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
|
|
| |
sources. Configuring doesn't always _do_ anything, which is why it's
a warning and not an error.
Submitted by: jkh
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
special ports building targets and will recurse properly. Sorry,
Julian E - no fancy prompts, just recursion! :-)
Added a `bundle' target. Purpose is as follows:
You want to give someone a complete tree sans distfiles (for
sticking on CDROM perhaps?) but the difficulty there is that
the first time the user types `make clean', all the unpacked
sources are gone again. Typing `make bundle' recreates the
original distfile if it can, so someone can "back up" their
unpacked tree easily with one command.
Whoops, just thought of something - it should warn if you
configured the working source.
Ok, next commit! :)
Submitted by: jkh
|
|
|
|
|
|
| |
thing with recursive build, configure, bundle or extract targets.
Reviewed by:
Submitted by:
|
|
|
|
|
| |
${PORTSDIR} too now - pass it to any and all config scripts.
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. New variable DEPENDS lets you list packages that this depends on,
relative to the top (lang/tcl, x11/tk, etc). These packages will
always get made first.
2. Don't configure again if you've already done so successfully.
3. Add pre-configure and post-configure hooks. You can now do a pre-configure,
a local configure, a port-provided configure and finally a post-configure
if you really really want to. I can't imagine anything this will leave us
not being able to do! :) [ Yes, I have actually found a use for at least
two of these in one port - see x11/tk!].
Submitted by: jkh
|
|
|
|
|
| |
was I thinking before..
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
|
| |
then run it even if GNU configure is to be run later.
Submitted by: jkh
|
|
|
|
|
| |
but fairly usable at this stage.
Submitted by: jkh
|
|
|
|
| |
- Install with group BINGRP, not BINOWN.
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
|
|
| |
have nuked it, not fixed it. No longer install /etc/localtime.
Reviewed by:
Submitted by:
|
|
|
|
|
| |
case it's a link (in which case the subsequent install will fall over).
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
|
|
|
| |
Submitted by: jkh
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Makefiles.
DANGER WILL ROBINSON!
This will cause repeat installs of certain programs, such as `init' and
`rcp', to fail unless one of the two conditions is met:
1) You are in single-user mode.
2) Your security level is set to 0 or -1.
If you have compiled a kernel from the latest sources, your kernel
security level is set to -1 by default, which will keep `init' from
fiddling with it. You can increase it, but not decrease it, from the
command line with the command `sysctl -w kern.securelevel=<new value>'.
I believe that -1 is the most appropriate value to use while we are still
developing the code, although when we ship it should be changed back to 0.
See init(8) for more information.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
have a choice between SHARED=copies and SHARED=symlinks. The default
is to copy.
I have also added a /usr/share/examples/etc directory, where I hope to
have all sample configuration files which in real use go into /etc installed.
(This way, if the user really screws the real one up, they can always go
back to a known-working distribution copy, even if they don't have sources.)
|
|
|
|
| |
Fixed the makefile.
|
| |
|
|
|
|
| |
location.
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
|
| |
|
| |
|
|
|
|
| |
as I can tell, this is ts the right thing to do.
|
|
|
|
| |
Killed a bunch of control chars.
|