From owner-freebsd-hackers Tue Jul 21 13:39:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06358 for freebsd-hackers-outgoing; Tue, 21 Jul 1998 13:39:46 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picasso.wcape.school.za ([196.21.102.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06265 for ; Tue, 21 Jul 1998 13:39:23 -0700 (PDT) (envelope-from pvh@leftside.wcape.school.za) Received: from uucp by picasso.wcape.school.za with local-rmail (Exim 1.92 #2) for freebsd-hackers@freebsd.org id 0yyjBV-0007Hh-00; Tue, 21 Jul 1998 22:38:53 +0200 Received: from localhost (pvh@localhost) by leftside.wcape.school.za (8.8.8/8.8.4) with SMTP id WAA01978 for ; Tue, 21 Jul 1998 22:38:02 +0200 (SAT) Date: Tue, 21 Jul 1998 22:38:01 +0200 (SAT) From: Peter van Heusden To: freebsd-hackers@FreeBSD.ORG Subject: Netscape Directory API port? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just compiled the 19980531 version of the Netscape Directory API code (it compiles with one tiny change on FreeBSD 2.2.6) and am considering turning it into a port. A couple of questions, though: 1) Is anyone actively working on such a port already? 2) Is anyone using the Directory API code? Are there any suggestions at to what should get installed where? 3) The libraries for the Netscape stuff will clash with the UMich stuff. Anyone wanting to work with LDAP will probably want to have both hanging around, to have both an API, and a server (esp. if the UMich server gets upgraded along the lines people on this list have suggested). Any ideas about how the conflict should be resolved? Hoping this doesn't sound clueless, Peter -- Peter van Heusden | Computers Networks Reds Greens Justice Peace Beer Africa pvh@leftside.wcape.school.za | Support the SAMWU 50 litres campaign! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message