*BSD News Article 87237


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.Hawaii.Edu!news.caldera.com!enews.sgi.com!news.sgi.com!news1.best.com!bofh.noc.best.net!not-for-mail
From: rone@bofh.noc.best.net (Ron Echeverri)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Removing leading path in FreeBSD Ports
Date: 22 Jan 1997 11:03:09 -0800
Organization: fidgety systems administrators gmbh
Lines: 25
Message-ID: <5c5o9d$4f8@bofh.noc.best.net>
References: <32E64DC1.41C67EA6@baynetworks.com>
NNTP-Posting-Host: bofh.noc.best.net
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34373

In article <32E64DC1.41C67EA6@baynetworks.com>,
Robert Withrow  <bwithrow@baynetworks.com> wrote:
>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?  ;-)

I got miffed too, so i did this:

bofh# ls -l /usr/ports/pub/FreeBSD/FreeBSD-current/ports
lrwxrwxr-x  1 root  wheel  10 Aug 31 00:00 /usr/ports/pub/FreeBSD/FreeBSD-current/ports@ -> /usr/ports

Works great ;)

rone
-- 
 Ron Echeverri         Best Internet Usenet Administration        rone@best.net
  ============================================================================
                         All bribes cheerfully accepted.