Date: Wed, 21 Jul 2010 17:45:20 +0400 From: Anonymous <swell.k@gmail.com> To: Sean <sean@gothic.net.au> Cc: Dominic Fandrey <kamikaze@bsdforen.de>, Doug Barton <dougb@FreeBSD.org>, Peter Jeremy <peterjeremy@acm.org>, Joe <joeb_722@comclark.com>, Janne Snabb <snabb@epipe.com>, freebsd-ports@freebsd.org Subject: Re: [new port] usage of shar command Message-ID: <86hbjtvthr.fsf@gmail.com> In-Reply-To: <5554CEAC-E199-4CBF-943B-D2C5C143E2F7@gothic.net.au> (sean@gothic.net.au's message of "Wed, 21 Jul 2010 23:31:51 %2B1000") References: <4C42CFDA.3040409@comclark.com> <4C42D292.208@infracaninophile.co.uk> <4C4388D2.30200@comclark.com> <alpine.BSF.2.00.1007190216290.9805@tiktik.epipe.com> <20100720190602.GA32624@server.vk2pj.dyndns.org> <alpine.BSF.2.00.1007201343310.1689@qbhto.arg> <4C465E14.1060300@comclark.com> <4C46EE76.10206@bsdforen.de> <5554CEAC-E199-4CBF-943B-D2C5C143E2F7@gothic.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean <sean@gothic.net.au> writes: >>> The text as its currently exists is a long way from being clear to a >>> first timer. And I am talking about the new change that just went in. >>> >>> "shar `find port_dir` (note the backticks)", >>> >>> or >>> >>> "shar $(find port_dir)" >> >> This one doesn't work in (t)csh, the backticks do. >> >>> both address the problem nicely. >>> >>> By all means go and make the correction. >> >> Object! >> > > find port_dir -print0 | xargs -0 -x shar > > Though it doesn't help when you've got too many files. Then you're probably better off with the tar command to generate shar files. BTW, do we still have *supported* release where tar(1) can't create shar archives?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86hbjtvthr.fsf>