From owner-freebsd-questions Mon Sep 9 12:39:52 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E132937B400; Mon, 9 Sep 2002 12:39:47 -0700 (PDT) Received: from sage-one.net (adsl-65-71-135-137.dsl.crchtx.swbell.net [65.71.135.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8ED443E65; Mon, 9 Sep 2002 12:39:46 -0700 (PDT) (envelope-from jackstone@sage-one.net) Received: from sagea (sagea [192.168.0.3]) by sage-one.net (8.11.6/8.11.6) with SMTP id g89JdjS88150; Mon, 9 Sep 2002 14:39:45 -0500 (CDT) (envelope-from jackstone@sage-one.net) Message-Id: <3.0.5.32.20020909143944.00fbeac8@mail.sage-one.net> X-Sender: jackstone@mail.sage-one.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 09 Sep 2002 14:39:44 -0500 To: Jerry Lundy , freebsd-questions@FreeBSD.ORG, re@FreeBSD.ORG From: "Jack L. Stone" Subject: Re: tbz vs. tgz In-Reply-To: <3D7CF27A.75728194@aafes.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 02:11 PM 9.9.2002 -0500, Jerry Lundy wrote: >Greetings. > >The change of package format from .tgz to .tbz has created a furor in my >office. Our pkg_add quit working, apparently due to the cutover. (I >would have assumed that a migration would be more appropriate.) > >Question: How do we make pkg_add work again? > >Better idea: Can freebsd.org make pkg_add work again? > >Thanks, > >Jerry W. Lundy, CISSP >AAFES Contractor: The Greentree Group 214-312-6638 > Wonder if putting this in your /etc/make.conf file would help for now: # PKG_SUFX=.tgz (...or whatever ... I don't pkg_add much, so haven't tried this) Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message