Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Jolly Roger <jollyroger@pobox.com>
Newsgroups: comp.sys.mac.system
Subject: Re: What usenet client are you using?
Date: 26 Feb 2015 18:32:31 GMT
Organization: People for the Ethical Treatment of Pirates
Lines: 27
Message-ID: <cl975uFiodtU1@mid.individual.net>
References: <54e3b0d4$0$53943$b1db1813$b96576b3@news.astraweb.com> <2015022217565993804-anon@anonumostorg> <mcfhvf$5b7$1@dont-email.me> <1m0c3t5.1avm35gu41jp3N%jamiekg@wizardling.geek.nz> <mcgqvv$7v3$1@dont-email.me> <1m0dbel.u1zves608k7eN%jamiekg@wizardling.geek.nz> <mcma02$15o$2@dont-email.me> <cl80tdF8n7sU1@mid.individual.net> <54ef226b$0$46561$c3e8da3$9b4ff22a@news.astraweb.com> <slrnmeueub.2376.g.kreme@kreme.eternal-september.org> <cl8t1uFe6amU10@mid.individual.net> <slrnmeulp2.27j6.g.kreme@kreme.eternal-september.org>
X-Trace: individual.net 6b1OcUnuNJGwtteb2Tnn9wGCQ3kUmhRO5Xvi/q40/mXQX33GBh
Cancel-Lock: sha1:cMqOHmzkwPBsjsbBvRx0aBQa2l4=
X-Face: _.g>n!a$f3/H3jA]>9pN55*5<`}Tud57>1<n@LQ!aZ7vLO_nWbK~@T'XIS0,oAJcU.qLM dk/j8Udo?O"o9B9Jyx+ez2:B<nx(k3EdHnTvB]'eoVaR495,Rv~/vPa[e^JI+^h5Zk*i`Q;ezqDW< ZFs6kmAJWZjOH\8[$$7jm,Ogw3C_%QM'|H6nygNGhhl+@}n30Nz(^vWo@h>Y%b|b-Y~()~\t,LZ3e up1/bO{=-)
User-Agent: slrn/1.0.1 (Darwin)
Xref: csiph.com comp.sys.mac.system:70261

On 2015-02-26, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
> Okay, so one time? In band camp? Jolly Roger <jollyroger@pobox.com> was all, like:
>> On 2015-02-26, Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:
>>> Okay, so one time? In band camp? Warren Oates <warren.oates@gmail.com> was all, like:
>>>
>>> [snip]
>>>
>>> Quick unrelated question, is it possible to get the command-line
>>> developer tools installed and working properly WITHOUT installing the
>>> many GB of XCode? I don't care on my main system, but on my laptop Xcode
>>> represents 10% of my SSD.
>
>> So go to https://developer.apple.com/downloads/ and download the
>> appropriate version of "Command Line Tools" for your system, and install
>> it.
>
> It seems the last time I tried this, it did not work. Perhaps that was
> only Macports that failed to work though.

MacPort shouldn't have anything to do with it. If MacPorts is causing a
malfunction, that's up to you to debug.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR