NOTICE: This package has been removed from pkgsrc

./audio/libopendaap, DAAP client library

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


Branch: CURRENT, Version: 0.4.0, Package name: libopendaap-0.4.0, Maintainer: pkgsrc-users

libopendaap is a library written in C which enables applications to
discover, and connect to, iTunes(R) music shares.

Unlike all other daap implementations, this library is able to connect
to recent iTunes shares which require a special authentication
algorithm.


Required to build:
[devel/libtool-base] [devel/pkg-config]

Master sites:

SHA1: 5fe4382af7ecc97a6cb510ebec87b40d6cf6ef38
RMD160: ed8732c6c487ef4902ff2d68552a66418cf2760d
Filesize: 236.282 KB

Version history: (Expand)


CVS history: (Expand)


   2009-03-05 22:49:13 by Soren Jacobsen | Files touched by this commit (11) | Package removed
Log message:
Remove libopendaap, which is dead upstream and has not been useful for years.
   2008-07-14 14:56:20 by Joerg Sonnenberger | Files touched by this commit (563)
Log message:
Mark as destdir ready.
   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-07-07 17:49:34 by Johnny C. Lam | Files touched by this commit (63)
Log message:
LIBTOOL_OVERRIDE generally doesn't need to be specified anymore... just
set OVERRIDE_DIRDEPTH to find any libtool scripts deeper in the WRKSRC
tree unless they're named something other than "libtool".

SHLIBTOOL_OVERRIDE generally doesn't need to be specified either -- just
define it to the empty list and shlibtool-override will look for libtool
scripts.
   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-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.