Commit graph

24 commits

Author SHA1 Message Date
joerg
f1a241d146 It is user-destdir, not user-destir. 2008-03-11 18:40:18 +00:00
jlam
4c8382aec0 Mechanical changes to add DESTDIR support to packages that install
their files via a custom do-install target.
2008-03-03 17:45:33 +00:00
wiz
b20d01b785 Reset maintainer, ben@ has resigned. 2006-12-15 14:34:18 +00:00
jlam
c16221a4db Change the format of BUILDLINK_ORDER to contain depth information as well,
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.

For example, "make show-buildlink3" in fonts/Xft2 displays:

	zlib
	fontconfig
	    iconv
	    zlib
	    freetype2
	    expat
	freetype2
	Xrender
	    renderproto
2006-07-08 23:10:35 +00:00
jlam
9430e49307 Track information in a new variable BUILDLINK_ORDER that informs us
of the order in which buildlink3.mk files are (recursively) included
by a package Makefile.
2006-07-08 22:38:58 +00:00
rillig
96fc47c14f Aligned the last line of the buildlink3.mk files with the first line, so
that they look nicer.
2006-04-12 10:26:59 +00:00
reed
5abef9be14 Over 1200 files touched but no revisions bumped :)
RECOMMENDED is removed. It becomes ABI_DEPENDS.

BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.

BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.

BUILDLINK_DEPENDS does not change.

IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".

Added to obsolete.mk checking for IGNORE_RECOMMENDED.

I did not manually go through and fix any aesthetic tab/spacing issues.

I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.

I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.

As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.

As discussed on tech-pkg.

I will commit to revbump, pkglint, pkg_install, createbuildlink separately.

Note that if you use wip, it will fail!  I will commit to pkgsrc-wip
later (within day).
2006-04-06 06:21:32 +00:00
jlam
81edaaa606 Create directories before installing files into them. 2005-06-16 06:57:37 +00:00
wiz
dd85a5a4e8 Add buildlink3 file. 2005-04-09 18:37:08 +00:00
wiz
5ff7813062 Convert to bl3, untested. 2005-04-05 11:11:05 +00:00
wiz
8658d1996c Sort. 2005-04-05 11:10:42 +00:00
agc
4a3d2f7ce2 Add RMD160 digests. 2005-02-23 22:24:08 +00:00
agc
dc52048e01 Move WRKSRC definition away from the first paragraph in a Makefile. 2004-01-20 12:07:06 +00:00
jmmv
2b07fc26d8 s/@netbsd.org/@NetBSD.org/ in MAINTAINER. 2003-12-24 09:53:47 +00:00
ben
0d43bf684d Update MAINTAINER email address. 2003-12-13 20:14:26 +00:00
ben
728528749a Change from using packaged install program and flags, to a do-install
target in pkgsrc, in order to have a better chance of installing on
Solaris and other platforms.
2003-12-13 16:20:09 +00:00
ben
f17d9833e5 Give these packages a higher chance to install on Solaris. 2003-12-11 20:16:10 +00:00
ben
29bbaa1677 Update MASTER_SITES and HOMEPAGE to www.snake.net. 2003-12-11 19:24:33 +00:00
martti
e69ab8c365 COMMENT should start with a capital letter. 2003-07-21 16:35:12 +00:00
wiz
04f62f706a Change address of maintainer per PR 22170. 2003-07-19 08:54:23 +00:00
jmmv
0916498c1b Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz. 2003-03-29 12:40:00 +00:00
wiz
e1e2ff0628 Replace collver@linuxfreemail.com with collver1@attbi.com.
Closes PRs 19516, 19517, 19518, 19519, 19520, 19521, 19522, 19523,
19524, 19525 and some more, perhaps.
2002-12-24 18:55:32 +00:00
zuntum
c72c1cf5f9 Move pkg/ files into package's toplevel directory 2001-11-01 00:57:41 +00:00
agc
00251c6491 Initial import of libmemmgr-1.04 into the packages collection.
Provided in PR 12581 by Ben Collver (collver@linuxfreemail.com)

MemMgr is a fairly trivial memory management library.  There
is little it does that cannot be done using routines in  the
C library.  (In fact, allocation and disposal is implemented
using C library routines.)  The purposes of MemMgr are  two-
fold.

(i)  Minimize  configuration  burden  on  applications  that
     dynamically allocate memory.  For instance, malloc() on
     some  systems  returns  a  char  pointer;  on others it
     returns a void pointer.  The  MemMgr  library  routines
     encapsulate  system-specific  configuration differences
     and exports a fixed interface which is  system-indepen-
     dent.  Once you compile and install it, you just use it
     without thinking about whether your UNIX is System V or
     BSD inspired.

(ii) Provide  two parallel sets of allocation routines which
     either return NULL  (for  applications  which  want  to
     check)  or panic (for applications which simply want to
     die) on allocation failures.  Panicking is  implemented
     using the ETM library, which introduces a dependency on
     the ETM distribution.  So be it.  I use ETM for all  my
     programs anyway
2001-04-27 12:10:40 +00:00