DragonFly BSD

CVS log for src/share/mk/Attic/bsd.dfport.mk

[BACK] Up to [DragonFly] / src / share / mk

Request diff between arbitrary revisions


Keyword substitution: kv
Default branch: MAIN


Revision 1.6
Wed Jun 28 21:37:37 2006 UTC (8 years, 1 month ago) by swildner
Branches: MAIN
CVS tags: HEAD
FILE REMOVED
Changes since revision 1.5: +1 -1 lines
Remove ports and dfports specific include files.

Revision 1.5: download - view: text, markup, annotated - select for diffs
Wed Apr 20 21:58:13 2005 UTC (9 years, 3 months ago) by okumoto
Branches: MAIN
CVS tags: DragonFly_RELEASE_1_4_Slip, DragonFly_RELEASE_1_4
Diff to: previous 1.4: preferred, unified
Changes since revision 1.4: +1 -2 lines
Stop exporting OSVERSION variable to enviornment via .makeenv.
This quiets a the warning that OSVERSION is from the commandline
when ports calls make recursively.

OSVERSION is only used by the make infrastructure, so anything that
references that variable would get it from make's global scope, or
would get it from a recursively called make which would have put
it into the env since it is in MAKEFLAGS.

Variables set in the command line and MAKEFLAGS are readonly, those
variables are also exported into the enviornment of make.  Nothing
in the makefiles are able to modified thier values. (POSIX)

This is compatible with .makeenv (soon to be .EXPORT:)
     o if variable does not exist create it and
       export it to the enviornment, as empty string.
     o if variable exists, export it to the enviornment
       with its value.
     o if variable that is exported is set after being
       exported, export its new value.

     o if variable is from command line or MAKEFLAGS
       do net change is value, or modify the enviornment.
       Emit a warning.

Revision 1.4: download - view: text, markup, annotated - select for diffs
Tue Feb 24 13:05:14 2004 UTC (10 years, 5 months ago) by joerg
Branches: MAIN
CVS tags: DragonFly_Stable, DragonFly_Snap29Sep2004, DragonFly_Snap13Sep2004, DragonFly_RELEASE_1_2_Slip, DragonFly_RELEASE_1_2, DragonFly_1_0_REL, DragonFly_1_0_RC1, DragonFly_1_0A_REL
Diff to: previous 1.3: preferred, unified
Changes since revision 1.3: +3 -2 lines
DFports cleanup part(1)

This removes the redefinition of PORTSDIR to /usr/dfports. We use the normal
/usr/ports and have a second variable DFPORTSDIR for DragonFly override ports.

Also fix the warning about an undefined command when invocing make for an
overriden port without specifying a target.

Revision 1.3: download - view: text, markup, annotated - select for diffs
Wed Nov 19 00:51:24 2003 UTC (10 years, 8 months ago) by dillon
Branches: MAIN
Diff to: previous 1.2: preferred, unified
Changes since revision 1.2: +12 -0 lines
Change the system name from 'FreeBSD' to 'DragonFly'.  We are now officially
DragonFly 1.0-CURRENT.  The change is fairly straight forward but involves
adding support for the 'DragonFly' OS type in various gnu contributed pieces
(typically configure based), as well as compiler and BFD support for building
GCC and friends (basically just copied the FreeBSD files for DragonFly).

Additionally, hack the ports makefiles with UNAME_xxx environment variables
so ports builds think its still a FreeBSD-4.8 system.  Otherwise most of the
ports will fail.

Revision 1.2: download - view: text, markup, annotated - select for diffs
Tue Sep 9 16:49:31 2003 UTC (10 years, 10 months ago) by dillon
Branches: MAIN
Diff to: previous 1.1: preferred, unified
Changes since revision 1.1: +1 -1 lines
rename /usr/dports to /usr/dfports.  Includes some CVS surgery.

Revision 1.1: download - view: text, markup, annotated - select for diffs
Mon Sep 8 23:39:23 2003 UTC (10 years, 10 months ago) by dillon
Branches: MAIN
Add bsd.dport.mk, which Makefile's in /usr/dports will use instead of
bsd.port.mk.  Modify bsd.port.mk to check for the existance of the same
port in /usr/dports and, if found, to cd into the dport and run the target
there.

NOTE: /usr/bin/relpath is required (see /usr/src/usr.bin/relpath).

Diff request

This form allows you to request diffs between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.

Log view options