Sebastian Dröge <[EMAIL PROTECTED]> writes: > On Fr, 2006-08-18 at 18:11 -0700, Russ Allbery wrote:
>> Did this replace netlibs, or is netlibs still also of interest? I seem >> to recall that CLI and .NET are two different ways of talking about the >> same general set of technology. > Yes, it replaces netlibs. netlibs is not used by any current package > anymore and clilibs was chosen because it describes the technology used > better. Okay, thanks, I've closed the other bug. >> is a good start, but contains little of use in actually verifying the >> contents of the control file. At least a syntax specification would seem >> to be in order here. > Ok, I'll add it there next week. So let's leave this bug open until the > cli policy became part of the policy, ok? :) Or at least until there's a specification for the clilibs file in the CLI policy, which would probably be enough. Thanks! -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
