*BSD News Article 87157


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.mel.connect.com.au!news.mel.aone.net.au!grumpy.fl.net.au!news.webspan.net!newsfeeds.sol.net!hammer.uoregon.edu!hunter.premier.net!news.mathworks.com!usenet.eel.ufl.edu!news-feed-1.peachnet.edu!paperboy.wellfleet.com!newsmaster
From: Robert Withrow <bwithrow@baynetworks.com>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Removing leading path in FreeBSD Ports
Date: Wed, 22 Jan 1997 12:26:25 -0500
Organization: Bay Networks, Inc.
Lines: 17
Message-ID: <32E64DC1.41C67EA6@baynetworks.com>
NNTP-Posting-Host: tuva.wellfleet.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.5-RELEASE i386)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34372

When I get a port from the FreeBSD web pages, the tar file
has long leading paths like:

  pub/FreeBSD/FreeBSD-current/ports/mail/procmail/

I try to keep things neat by keeping these ports in my
own port directory, but I have to manually trim off
the pub/FreeBSD/FreeBSD-current/ports part, which is annoying.

Am I missing some nifty tar argument that would do this
automatically?  Is there some other way of dealing with
this short of creative symlinks?  Am I the only person
who gets miffed about this?  ;-)

-- 
Robert Withrow -- (+1 508 436 8256)
BWithrow@BayNetworks.com