NOTICE: This package has been removed from pkgsrc

./devel/libdfui, LIBrary for DragonFly User Interfaces

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ]

Branch: CURRENT, Version: 4.2, Package name: libdfui-4.2, Maintainer: joerg

libdfui is a LIBrary for DragonFly User Interfaces. It provides a highly
abstract user interaction interface with which an application program
(termed the backend) can communicate with a user via a concreate user
interface terminal program (termed the frontend.) The frontend and the
backend can communicate over several kinds of transport layers (TCP,
CAPS, and Named Pipes.) The protocol is abstract enough so that the
frontend can occupy nearly any medium (GUI, addressable text console,
teletype, voice synthesis/recognition, etc) with little to no `fudging'
of the semantics (i.e. the structure and nature of the information that
the backend wishes to present and/or acquire.)


Required to run:
[devel/libaura]

Required to build:
[devel/libtool-base]

Master sites:

SHA1: 952e7c16c7ed9e8a047b8c905e8ecd3193849cb0
RMD160: ba394dc2eb16f5b3161532196624b88b4f195091
Filesize: 22.024 KB

Version history: (Expand)

CVS history: (Expand)


   2007-07-16 23:38:40 by Joerg Sonnenberger | Files touched by this commit (6) 
Log message:
Update master site to reflect move of my server.
   2006-07-09 01:11:17 by Johnny C. Lam | Files touched by this commit (877) 
Log message:
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-09 00:39:49 by Johnny C. Lam | Files touched by this commit (877) 
Log message:
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-04-12 12:27:47 by Roland Illig | Files touched by this commit (749) 
Log message:
Aligned the last line of the buildlink3.mk files with the first line, so
that they look nicer.
   2006-04-10 17:03:29 by Joerg Sonnenberger | Files touched by this commit (1) 
Log message:
Fix include path (devel, not wip).
   2006-04-10 16:58:48 by Joerg Sonnenberger | Files touched by this commit (7) 
Log message:
Sync in libdfui-4.2 from pkgsrc-wip.
   2006-04-06 08:23:06 by Jeremy C. Reed | Files touched by this commit (1147) 
Log message:
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-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257) 
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.