Date: Tue, 29 Apr 1997 10:13:28 -0700 (PDT) From: Paul Traina <pst@jnx.com> To: FreeBSD-gnats-submit@freebsd.org Cc: jkh@freebsd.org Subject: bin/3418: pkg_create doesn't always create gzip'ed tarball Message-ID: <199704291713.KAA17508@base.jnx.com> Resent-Message-ID: <199704291720.KAA26934@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 3418 >Category: bin >Synopsis: pkg_create doesn't always create gzip'ed tarball >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 29 10:20:01 PDT 1997 >Last-Modified: >Originator: Paul Traina >Organization: Juniper Networks >Release: FreeBSD 2.2-STABLE i386 >Environment: 2.2 stable post 2.2.1 >Description: If I create a package with the name foo-beta-1.0 using the pkg_add command: pkg_create -v -f pkg/PLIST -c pkg/COMMENT -d pkg/DESC \ foo-beta_1.0 I end up with a file called "foo-beta_1.0" that is in .tar format, even though I get the message "creating gzip'ed tarball in ...". If I do the same command, with a different name: pkg_create -v -f pkg/PLIST -c pkg/COMMENT -d pkg/DESC \ foo-beta_1_0 a file called foo-beta_1_0.tgz is created which /is/ a gzipped tarball. My half-assed guess w/o looking at the source code is that someone's trying to do some suffix stripping. >How-To-Repeat: >Fix: I don't care if the final product says .tgz or not, but it should be consistent on gzipping the tarball, and this behavior needs to be documented. Ideally, it should always create a .tgz file, so there's no need to change the documentation. :-) >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704291713.KAA17508>