Makefile.inc: Rework automatic backup (bug 2527)

There were three main problems with the recently added backup feature:
1. It didn't work over NFS
2. It didn't work when a non-root built world the s

Makefile.inc: Rework automatic backup (bug 2527)

There were three main problems with the recently added backup feature:
1. It didn't work over NFS
2. It didn't work when a non-root built world the second time
3. It didn't use DESTDIR which had potential to conflict backups

It also previously featured "NO_BACKUP" which turned off the automatic
backup feature. To fix the #2 problem, the install timestamp has been
removed, so to avoid unwanted backups for multiple installworlds after
one buildworld, the user needs to pass NO_BACKUP in the command line.

This patch was contributed by Thomas Nikolajsen with minor modifications
added by John Marino.

http://bugs.dragonflybsd.org/issues/2527

show more ...

build: implement automatic world backups

The directives DAYS_BACKUP and NO_BACKUP have been removed.
The "backupworld" target will save important directories to the WORLD_BACKUP
directory just as be

build: implement automatic world backups

The directives DAYS_BACKUP and NO_BACKUP have been removed.
The "backupworld" target will save important directories to the WORLD_BACKUP
directory just as before, and it is restored with the "restoreworld" target.

Additionally, every time the "installworld" target is executed, the same
directories will be automatically backed up at the location of
${MAKEOBJDIRPREFIX}/world_backup . These directories could be restored
with the new make target "restoreworld-auto".

The WORLD_BACKUP location default is now /var/backups/world_backup .
The directory /usr/lib has been added to the backup list.
The more useless errors seen with a broken world have been removed, these
came in with bmake.

show more ...

build: add "make backupworld" and "make restoreworld" functionality

Three new make.conf parameters have been defined:
* WORLD_BACKUP - location to store backed up world binaries

build: add "make backupworld" and "make restoreworld" functionality

Three new make.conf parameters have been defined:
* WORLD_BACKUP - location to store backed up world binaries
default = /var/backups/world_binaries
* DAYS_BACKUP - The number of days since the last backup that must pass
before "make installworld" fails with an error
default = 28
* NO_BACKUP - defining this will prevent backup checks.

The build functionality has been changed. Prior to "make installworld",
the makefile will check to see if system binaries have been previously
backed up. If they haven't, "make installworld" will fail to execute
explaining that the system should be backed up. If a previous backup
does exist, but it's older than the specified number of days, "make
installworld" will fail explaining the backup needs to be refreshed.

Passing NO_BACKUP through the command line or make.conf will inhibit
these checks.

While here, define WORLD_CCVER, LDVER, WORLD_LDVER, WORLD_BINUTILSVER
in make.conf man page too.

show more ...

Replace legacy make with bmake

The proper way to detect which make is building the makefile is to check
for .PARSEDIR. If present, bmake is processing the makefile. For the
time being, both make w

Replace legacy make with bmake

The proper way to detect which make is building the makefile is to check
for .PARSEDIR. If present, bmake is processing the makefile. For the
time being, both make will be supported for bootstrapping purposes, but
in time the check can be removed, say for the DragonFly 3.6 release.

The abundance of .ORDER commands in bsd.dep.mk caused a breakage when
building world in parallel with bmake. Likely some order constraints
were impossible to achieve, and bmake just stopped while legacy did the
best it could. In any case, the majority of the .ORDER commands were
replaced by a single .ORDER command which solved the problem.

The legacy make is disconnected in this commit set, but the source files
will be removed soon.

show more ...

/usr/src/Makefile: Remove duplicate target.

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.

rename amd64 architecture to x86_64

The rest of the world seems to call amd64 x86_64. Bite the bullet and
rename all of the architecture files and references. This will
hopefully make pkgsrc build

rename amd64 architecture to x86_64

The rest of the world seems to call amd64 x86_64. Bite the bullet and
rename all of the architecture files and references. This will
hopefully make pkgsrc builds less painful.

Discussed-with: dillon@

show more ...

Revert "rename amd64 architecture to x86_64"

This reverts commit c1543a890188d397acca9fe7f76bcd982481a763.

I'm reverting it because:
1) the change didn't get properly discussed
2) it was based on

Revert "rename amd64 architecture to x86_64"

This reverts commit c1543a890188d397acca9fe7f76bcd982481a763.

I'm reverting it because:
1) the change didn't get properly discussed
2) it was based on false premises:
"The rest of the world seems to call amd64 x86_64."
3) no pkgsrc bulk build was done to test the change
4) the original committer acted irresponsibly by committing
such a big change just before going on vacation.

show more ...

rename amd64 architecture to x86_64

The rest of the world seems to call amd64 x86_64. Bite the bullet and
rename all of the architecture files and references. This will
hopefully make pkgsrc build

rename amd64 architecture to x86_64

The rest of the world seems to call amd64 x86_64. Bite the bullet and
rename all of the architecture files and references. This will
hopefully make pkgsrc builds less painful.

Discussed-with: dillon@

show more ...

remove gcc34

Remove the distribute, redistribute and distributeworld targets.

We don't split things into different distributions and none of this
was ever used.

Pointed-out-by: pavalos

Release Engineering: Update master to 2.3.0-DEVELOPMENT

2.0 Release Engineering:

* cvsup file, slip tag target

Enforce proper sequencing of world and kernel targets.

.ORDER: does *not* take an arbitrary list of targets of which all pairs
are supposed to be built in their specified sequence,
instead it specif

Enforce proper sequencing of world and kernel targets.

.ORDER: does *not* take an arbitrary list of targets of which all pairs
are supposed to be built in their specified sequence,
instead it specifies which adjacent pairs need to be built in sequence.
As a result, given a sequence "buildworld buildkernel quickkernel" and
the make targets "buildworld" and "quickkernel", make would still
parallelize the build of these targets.

Additionally, introduce quickworld to the sequencing.

show more ...

Release engineering, Add a slip target to /usr/src/Makefile for 1.12 and
add a cvsup example file for 1.12.

release engineering: Add a slip tag for 1.10 and add an example cvsup
file for 1.10.

Setup for 1.8 release - add new targets to Makefile to udpate the slip tag
for 1.8, and add a new cvsup example file for 1.8.

* s/FreeBSD/DragonFly/

* Fix spelling & grammar mistakes.

Submitted-by: Trevor Kendall <trevorjkendall@gmail.com>

Update upgrade procedure and adjust disk usage.

Add a new target for cvs administration of the 1.6 slip tag. Add a cvsup
file example that will maintain a 1.6 release.

Add a target that will update the 1.4-release slip tag.

Add 'manlint' (from bsd.man.mk) to the top level targets.

Add -d /cvs to tag update targets.

Add some additinal targets to allow elements of a buildworld to be
independantly built. This is for debugging only.

Don't expand CCVER when testing for its definition.