[OSX-Users] Re: Apple purging GPL?

[Michael Jewell]

Apparently it comes with  "grep (BSD grep) 2.5.1-FreeBSD" instead of
"grep (GNU grep) 2.5.1" (though I've not confirmed this myself).

Cheers,
Mike

On Fri, Aug 31, 2012 at 5:05 PM, Steve Harris <swh at me.com> wrote:
> Wait, grep?!
>
> Tell me there's a grep command line tool in MLion?
>
> - Steve
>
> On 2012-08-31, at 16:49, Leslie Carr wrote:
>
>> I'm not titillated by the license wars, but i thought it worth going back to the original lists and looking at the full range of source packages that have been used in OS X historically.
>>
>> Here's how many packages have been used in each major release:
>> 10.1  167
>> 10.2  210
>> 10.3  263
>> 10.4  348
>> 10.5  375
>> 10.6  329
>> 10.7  289
>> 10.8  222
>>
>> Why is it decreasing over the last few releases? Which specific packages have gone? Are they obsolete? Or is Apple fiendishly replacing them with horrible proprietary code (bwah ha ha ha ha)?
>>
>> Here's the list of packages that have disappeared from Mountain Lion. How do you read it?
>> ChatServer
>> CyrusIMAP
>> DSTools
>> DirectoryService
>> Libm
>> OpenDirectory
>> SpamAssassin
>> WebmailServer
>> X11apps
>> X11fonts
>> X11libs
>> X11misc
>> X11proto
>> X11server
>> amavisd
>> apache_mod_bonjour
>> apache_mod_bw
>> apache_mod_encoding2
>> apache_mod_jk
>> apache_mod_python
>> bootstrap_cmds
>> clamav
>> developer_cmds
>> dovecot
>> enscript
>> fetchmail
>> flex
>> grep
>> headerdoc
>> libmd
>> libsecurity_apple_csp
>> libsecurity_apple_cspdl
>> libsecurity_apple_file_dl
>> libsecurity_apple_x509_cl
>> libsecurity_apple_x509_tp
>> libsecurity_asn1
>> libsecurity_authorization
>> libsecurity_cdsa_client
>> libsecurity_cdsa_plugin
>> libsecurity_cdsa_utilities
>> libsecurity_cdsa_utils
>> libsecurity_checkpw
>> libsecurity_cms
>> libsecurity_codesigning
>> libsecurity_cssm
>> libsecurity_dotmacdl
>> libsecurity_filedb
>> libsecurity_filevault
>> libsecurity_keychain
>> libsecurity_ldap_dl
>> libsecurity_manifest
>> libsecurity_mds
>> libsecurity_ocspd
>> libsecurity_pkcs12
>> libsecurity_sd_cspdl
>> libsecurity_smime
>> libsecurity_ssl
>> libsecurity_utilities
>> libsecurityd
>> mailman
>> nasm
>> neon
>> netinfo
>> notify
>> subversion
>> tcp_wrappers
>> texi2html
>> xelf
>>
>>
>> --
>> Les
>>
>>
>> On 30 Aug 2012, at 12:14, Hugh Glaser <hg at ecs.soton.ac.uk>
>> wrote:
>>
>>> Really nice, sensible discussion - Chris noting that he is not a typical user, and Steve thinking about what's best for dads, etc..
>>> And about such a contentious subject.
>>>
>>> it would be nice if the other lists I see could manage that.
>>>
>>> On 30 Aug 2012, at 10:06, Steve Harris <swh at me.com>
>>> wrote:
>>>
>>>> On 2012-08-30, at 09:00, Chris Andrews wrote:
>>>>>
>>>>> On 30 Aug 2012, at 08:13, Luke Teacy <wtlt at ecs.soton.ac.uk> wrote:
>>>>>
>>>>>> Only danger is, what else does it allow them to do? As much as I love my iOS devices, I'm in no hurray to see it running on my Mac - at least not in a way that prevents me bringing up a bash shell and doing most of the things I can do on Linux.
>>>>>
>>>>> Starting from nothing and making a closed platform is a lot easier than taking an open platform and making it closed. Jailing OS X a la iOS is going to be almost impossible without some kind of get-out for developers, power users and people who like emacs.
>>>>
>>>> I think the most likely outcome would be that by default it's locked down à la iOS, but if you click the "power user" button you can run arbitrary code.
>>>>
>>>> It kind of rubs me up the wrong way, but it would probably be for the best - people like my Dad might finally stop installing random crap software they find lying about and binning PCs every year because they're crammed with malware.
>>>>
>>>> - Steve
>>>
>>>
>>
>>
>
>

-- 
Dr Michael O. Jewell
ECS, University of Southampton