From owner-freebsd-arch@FreeBSD.ORG  Thu Feb  5 14:31:08 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D1E1416A4CE
	for <arch@freebsd.org>; Thu,  5 Feb 2004 14:31:08 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5875443D39
	for <arch@freebsd.org>; Thu,  5 Feb 2004 14:31:07 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id i15MUqN4003145;
	Thu, 5 Feb 2004 23:30:57 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: "M. Warner Losh" <imp@bsdimp.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 05 Feb 2004 07:45:49 MST."
             <20040205.074549.128866887.imp@bsdimp.com> 
Date: Thu, 05 Feb 2004 23:30:52 +0100
Message-ID: <3144.1076020252@critter.freebsd.dk>
cc: sam@errno.com
cc: arch@freebsd.org
Subject: Re: Resolving the crypto duplicity... 
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Feb 2004 22:31:08 -0000

In message <20040205.074549.128866887.imp@bsdimp.com>, "M. Warner Losh" writes:
>In message: <38921.1075966216@critter.freebsd.dk>
>            "Poul-Henning Kamp" <phk@phk.freebsd.dk> writes:
>: But as I said, it may be time to discuss the overall issue of kld
>: dependencies, rather than just scratch my own little itch...
>
>Typically people just put the module dependency into their kld and get
>on with their lives.  There's really little to discuss except maybe
>making an opencrypto module...  At least as far as the dependency
>issue with klds.  I have no comment on the code duplication aspects.

And that means that "optional dependencies" are not in the picture ?

I want gbde to use opencrypto if it is there, but I do not want to
require it (since it is optional from GBDE's point of view).

Is there any sane way to do that ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.