Commit graph

15 commits

Author SHA1 Message Date
rillig
f3d1383cd6 libgcrypt is needed for building programs, as reported in PR 37361. 2007-11-11 21:53:57 +00:00
gdt
41594ba91b bl3 on gettext-lib, PKGREVISION++ 2007-08-30 17:20:06 +00:00
gdt
bf66f721c7 Update to 3.1.0.
Override libtool; otherwise the distfile libtool inexplicably gets the
wrong shlib version.

Changes since 3.0.0:

- Added fragmentation support for large messages
- Added new method for buddy authentication which does not require the
  (explicit) use of fingerprints.
2007-08-02 11:26:28 +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
salo
8201d5e4be Update to version 3.0.0
From Jason White, via PR pkg/32451

Changes:

- Support for OTR protocol version 2; will still interoperate with version 1
  clients (though with a warning to the user), fixes identity-binding flaw
  http://www.cypherpunks.ca/otr/Protocol-v2-3.0.0.html
2006-02-13 14:44:31 +00:00
joerg
5911def816 Recursive revision bump / recommended bump for gettext ABI change. 2006-02-05 23:08:03 +00:00
gdt
58a5ca2edf remove "BUILDLINK_DEPMETHOD.libotr?= build", because depending
packages can dynamically link libotr and thus must depend on it.

reviewed by wiz@
2005-09-09 23:45:27 +00:00
rillig
96b8e019fa Added a patch to fix void* arithmetic. 2005-07-30 21:30:53 +00:00
gdt
3b5869a4e1 update to 2.0.2:
* src/privkey.c (otrl_privkey_hash_to_human): Avoid writing a
        NUL one byte past the end of the buffer
2005-07-27 19:17:35 +00:00
tv
f816d81489 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:44:48 +00:00
nathanw
38f0a4f400 I put this package in security, not chat; update the buildlink file to
match.
2005-03-25 17:21:26 +00:00
nathanw
9814b8da9f Initial import of libotr-2.0.1.
This is the portable OTR Messaging Library, as well as the toolkit to
help you forge messages.

Off-the-Record (OTR) Messaging allows you to have private
conversations over instant messaging by providing:

Encryption
    No one else can read your instant messages.
Authentication
    You are assured the correspondent is who you think it is.
Deniability
    The messages you send do not have digital signatures that are
    checkable by a third party. Anyone can forge messages after a
    conversation to make them look like they came from you. However,
    during a conversation, your correspondent is assured the messages
    he sees are authentic and unmodified.
Perfect forward secrecy
    If you lose control of your private keys, no previous conversation
    is compromised.
2005-03-24 21:24:12 +00:00