Hi,
Bill Cole wrote:
Because running the tools it provides in a VM is a grotesque waste of
RAM and disk space and puts a wall up between tools I want to use
occasionally and the UI where I prefer to work mostly.
I second that, for me a VM is a waste and only the "last possible mean".
Except
Hi Ryan,
Ryan Schmidt wrote:
I agree, I don't see CGContextCopyPath described in the 10.5 SDK headers.
I've encountered this in other situations. Apple documentation's notion of when
a symbol became available seems to refer to the libraries, not necessarily the
headers. Sometimes they introdu
To complement people answer, and most of all, "Why macOS"? Well, because
there is not another Unix laptop that is as efficiently implemented. For
example, take a Windows laptop, put Linux on it, and see your battery life
drop at least of 15-20%. Well, i hate it. On my macOS I have very good
battery
On Tue, 19 Feb 2019 at 14:13, S. L. Garwood via macports-users wrote:
>
> So my philosophical question is “Why MacPorts these days?”.
If your question is: "Why a package manager for Mac these days", just
a few numbers.
We don't have any good analytics data, but our competitor saw more
than 6 mill
A big thank you to all the people who chimed in and gave me much to think over.
I have used MacPorts since 10.6.8 - it is based on one of my favorite package
managers (FreeBSD ports)
I’ve been a long time FreeBSD user, fan, and booster (since 386-bsd believe it
or not).
I think for now I’ll keep
> On 20 Feb 2019, at 8:00 pm, macports-users-requ...@lists.macports.org wrote:
>
>
> OK
> Your inbox has 14500 mail.
> mail->backup size exceeded (after 20%)
>
> So I was trying to save all your mail using thunderbird
>
> The flash in the corner was “m...@tigger.ws: junk mail” not as in mail
> On 20 Feb 2019, at 8:00 pm, macports-users-requ...@lists.macports.org wrote:
>
> First let me say I have used MacPorts since 10.6.8.
>
> Recently, given the overall Apple direction for MacOS I stopped and asked
> myself “Why am I doing this?”.
> I started using Mint Linux on VirtualBox and
On Wed, Feb 20, 2019 at 7:15 AM Mojca Miklavec wrote:
>
> I would have left macOS if I didn't have a package manager available,
> the computer would be next-to-useless.
Speaking as an ordinary end-user I agree with that; if not for macports I’d
be even more tempted to switch to FreeBSD myself.
> Am 20.02.2019 um 14:50 schrieb S. L. Garwood via macports-users
> :
>
> A big thank you to all the people who chimed in and gave me much to think
> over.
> I have used MacPorts since 10.6.8 - it is based on one of my favorite package
> managers (FreeBSD ports)
> I’ve been a long time FreeB
On Tue, Feb 19, 2019 at 8:13 AM S. L. Garwood via macports-users <
macports-users@lists.macports.org> wrote:
> First let me say I have used MacPorts since 10.6.8.
>
> [...]
> I appreciate all the work the developers have put into MacPorts but to me
> the handwriting on the wall was when Apple pul
On 20 Feb 2019, at 10:10, Alejandro Imass wrote:
On Tue, Feb 19, 2019 at 8:13 AM S. L. Garwood via macports-users <
macports-users@lists.macports.org> wrote:
First let me say I have used MacPorts since 10.6.8.
[...]
I appreciate all the work the developers have put into MacPorts but
to me
On Wed, 20 Feb 2019 at 16:33, Bill Cole wrote:
>
> The departure of MacPorts from Mac OS Forge as it was
> being wound down was announced in
> https://lists.macports.org/pipermail/macports-dev/2016-August/033405.html
While I wouldn't mind if Apple continued to provide hardware building
capacity, t
I agree, the project is strong. Apple providing a server was nice, but
certainly not a necessity. GitHub is great!
Sent from my iPhone
> On Feb 20, 2019, at 7:47 AM, Mojca Miklavec wrote:
>
>> On Wed, 20 Feb 2019 at 16:33, Bill Cole wrote:
>>
>> The departure of MacPorts from Mac OS Forge as
On Wed, 20 Feb 2019, Mojca Miklavec wrote:
I would have left macOS if I didn't have a package manager available,
the computer would be next-to-useless.
I'm probably not the only one here who remembers the days when you got
your software from comp.sources and figured out how to make it go :-)
On Wed, Feb 20, 2019 at 10:48 AM Mojca Miklavec wrote:
> On Wed, 20 Feb 2019 at 16:33, Bill Cole wrote:
> >
> > The departure of MacPorts from Mac OS Forge as it was
> > being wound down was announced in
> >
> https://lists.macports.org/pipermail/macports-dev/2016-August/033405.html
>
> While I w
On 20 Feb 2019, at 16:23, Alejandro Imass wrote:
On Wed, Feb 20, 2019 at 10:48 AM Mojca Miklavec
wrote:
On Wed, 20 Feb 2019 at 16:33, Bill Cole wrote:
The departure of MacPorts from Mac OS Forge as it was
being wound down was announced in
https://lists.macports.org/pipermail/macports-dev
> On 20 Feb 2019, at 8:00 pm, macports-users-requ...@lists.macports.org wrote:
>
>>>
>>> So my philosophical question is “Why MacPorts these days?”.
>>
>> Same reason as always: to help you install software on your Mac. If
>> you prefer installing software in a VM running a different OS, by
> On 20 Feb 2019, at 8:00 pm, macports-users-requ...@lists.macports.org wrote:
>
>> So my philosophical question is “Why MacPorts these days?”
>
> Because running the tools it provides in a VM is a grotesque waste of
> RAM and disk space and puts a wall up between tools I want to use
> occas
On 20 Feb 2019, at 18:56, James Linder wrote:
On 20 Feb 2019, at 8:00 pm, macports-users-requ...@lists.macports.org
wrote:
So my philosophical question is “Why MacPorts these days?”
Because running the tools it provides in a VM is a grotesque waste of
RAM and disk space and puts a wall up b
19 matches
Mail list logo
