Date: Tue, 4 Jun 2002 13:36:17 +1000 From: "Tim J. Robbins" <tjr@FreeBSD.ORG> To: Paul Herman <pherman@frenchfries.net> Cc: current@FreeBSD.ORG, re@FreeBSD.ORG, cvs@FreeBSD.ORG Subject: Re: Updating GNU Tar in the base system Message-ID: <20020604133617.A42142@treetop.robbins.dropbear.id.au> In-Reply-To: <20020603151118.X80740-100000@mammoth.eat.frenchfries.net>; from pherman@frenchfries.net on Mon, Jun 03, 2002 at 03:14:23PM -0700 References: <3CFBCA0A.32542302@FreeBSD.org> <20020603151118.X80740-100000@mammoth.eat.frenchfries.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 03, 2002 at 03:14:23PM -0700, Paul Herman wrote: > On Mon, 3 Jun 2002, Maxim Sobolev wrote: > > > However, before proceeding I would like to get an advice with regard > > to the most appropriate procedure for doing the upgrade. > > This came up in another list somewhere (don't know off hand), but > you might also consider having tar wrap around pax. I am in favour of doing this. Same with cpio. I'd prefer to see GNU tar and cpio in ports (if they are not already there). If the functionality of a GNU long option is useful, we should find an option letter that isn't used, or use the -W namespace. Another similar move would be to make /usr/bin/compress act as gzip, gunzip, etc. by using zlib - OpenBSD have done this, but it is temporarily disabled. Having two tar's, two cpio's, two awk's, gzip and zlib in the base system is bloat. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020604133617.A42142>