Received: with LISTAR (v1.0.0; list gopher); Wed, 16 Jan 2002 10:33:55 -0500 (EST) Return-Path: Delivered-To: gopher@complete.org Received: from erwin.complete.org (cc62016-a.indnpls1.in.home.com [24.36.182.146]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "erwin.complete.org", Issuer CN "John Goerzen -- Root CA" (verified OK)) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 04FE93B80B; Wed, 16 Jan 2002 10:33:55 -0500 (EST) Received: by erwin.complete.org (Postfix, from userid 1000) id C41C67582B; Wed, 16 Jan 2002 10:33:54 -0500 (EST) To: gopher@complete.org Cc: , ripclaw@rocklinux.org Subject: [gopher] Re: Antwort: Re: finally i find other gopherfans... (gn maintainer) References: From: John Goerzen Date: Wed, 16 Jan 2002 10:33:54 -0500 In-Reply-To: ("Stefan Koerner"'s message of "Tue, 15 Jan 2002 19:01:54 +0100") Message-ID: <87ofjuqpi5.fsf@complete.org> Lines: 31 User-Agent: Gnus/5.090005 (Oort Gnus v0.05) XEmacs/21.4 (Common Lisp, alpha-debian-linux) MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-archive-position: 339 X-listar-version: Listar v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Listar version 1.0.0 X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher "Stefan Koerner" writes: > i know that they work by having you name the number of byte to copy, > but the glibc documentation for it was too sketchy and the differences > between e.g. the various *nprintf variants and the internally used form= > ats > did not clearly arise into my mind after reading the documentation > and the usual glibc cruft. > especially i did not see where the usage/performance advantages where a= > t. Hmm, that's a bit too general for me to answer, I think... if you've got some more specific questions, feel free to ask. However, I can state that the performance implications are almost always so negligable as to be irrelevant. > did anything fundamental (e.g. protocol extensions) change ? > anything that could possibly break compatibility is of interest. No. What I meant was to look over the diffs where the CVS logs talk about "security" and see how the code was modified to make it more secure, and apply those same principles to gn. > i`m sure it is about library locations and ./configure options I need. > if i run into anything unusual, i`ll tell you, else i`ll try packaging > if for rocklinux soon. I want it to be possible to install with "./configure; make; make install" without patches on as many platforms as possible, so if it doesn't work that way for you, I'd like to hear about it.