From owner-freebsd-current Sat May 18 21:29:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA20531 for current-outgoing; Sat, 18 May 1996 21:29:02 -0700 (PDT) Received: from nervosa.com (root@nervosa.com [192.187.228.86]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA20522 for ; Sat, 18 May 1996 21:28:59 -0700 (PDT) Received: from onyx.nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by nervosa.com (8.7.5/8.7.3) with SMTP id VAA18714 for ; Sat, 18 May 1996 21:28:51 -0700 (PDT) Date: Sat, 18 May 1996 21:28:43 -0700 (PDT) From: invalid opcode To: freebsd-current@freebsd.org Subject: catman Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's obvious that catman is a Good Thing (tm), _except_ for the fact that the old man files are still laying around. I have come to my own conclusion that they are still needed because of makewhatis(1). I know it's possible to catman a binarie's, etc's, manpages instead of just gzip -9'ing them while doing a make world. Not only would this leave us with possibly smaller, or possibly bigger manpages, but they would be a whole lot faster, and the space savings would be about the same as having the old manpages. The only thing I can think of as a hinderance to this is makewhatis. Maybe we should make catman take on the responsibility of makewhatis, so at the time we catman a manpage, we also write an entry to /usr/share/man/whatis. Opinions wanted. == Chris Layne ======================================== Nervosa Computing == == coredump@nervosa.com ================ http://www.nervosa.com/~coredump ==