Ryan Schmidt wrote:
> On Apr 5, 2021, at 17:16, Bjarne D Mathiesen wrote:
>>
>> 1) what's our audience :
>> ? newbies
>> ? experienced
>> ? nerds
>> ? linux refugees
>> each of these needs different kinds of handholding
>>
>> There's also a tendency to just abandon problems and wait for u
On Apr 5, 2021, at 17:16, Bjarne D Mathiesen wrote:
> As I see it, we've got several problems/issues :
>
> 1) what's our audience :
> ? newbies
> ? experienced
> ? nerds
> ? linux refugees
> each of these needs different kinds of handholding
>
> 2) how does one use macports in daily
On Apr 5, 2021, at 16:33, Jonathan Stickel wrote:
> On 4/5/21 14:17, Ryan Schmidt wrote:
>> On Apr 5, 2021, at 14:43, Jonathan Stickel wrote:
>>> I'm working on updating the graphviz portfile.
>> Huh, I thought an update had already been submitted months ago.
>
> No, as per discussion on the t
As I see it, we've got several problems/issues :
1) what's our audience :
? newbies
? experienced
? nerds
? linux refugees
each of these needs different kinds of handholding
2) how does one use macports in daily life ?
we've got a section :
https://trac.macports.org/wiki/
On 4/5/21 14:17, Ryan Schmidt wrote:
On Apr 5, 2021, at 14:43, Jonathan Stickel wrote:
I'm working on updating the graphviz portfile.
Huh, I thought an update had already been submitted months ago.
No, as per discussion on the ticket:
https://trac.macports.org/ticket/62165
(I see you m
> Am 05.04.2021 um 22:17 schrieb macports-dev-requ...@lists.macports.org:
>
> Date: Mon, 5 Apr 2021 20:51:23 +0200
> From: Nils Breunese
> To: MacPorts Developers
> Subject: Re: Desolate Condition
> Message-ID:
> Content-Type: text/plain; charset=utf-8
>
> A more scalable solution would
On Apr 3, 2021, at 19:21, Wowfunhappy wrote:
>
> I know it's just one data point, but I thought the replies I got on this
> Hacker News comment today were interesting. I can understand why he/she got
> confused, and I wonder if there's anything MacPorts could do to make it
> clearer. https:/
On Apr 5, 2021, at 13:04, Karl-Michael Schindler wrote:
> 2) Put the command 'port install PACKAFE_NAME' to a prominent position.
https://github.com/macports/macports-webapp/issues/144
On Apr 5, 2021, at 14:43, Jonathan Stickel wrote:
> I'm working on updating the graphviz portfile.
Huh, I thought an update had already been submitted months ago.
> The new download link is:
>
> https://gitlab.com/graphviz/graphviz/-/package_files/8183714/download
>
> I can get Macports to
I'm working on updating the graphviz portfile. The new download link is:
https://gitlab.com/graphviz/graphviz/-/package_files/8183714/download
I can get Macports to download it by using:
master_sites https://gitlab.com/${name}/${name}/-/package_files/8183714
distfiles download
But the dow
Karl-Michael Schindler wrote:
> This indicates the first problem: Brew is often better represented on
> homepages of other software than MacPorts. The task to tackle is to find a
> person or form a team going after this.
A more scalable solution would be for port maintainers to check the upstr
Am 05.04.2021 um 14:00 schrieb macports-dev-requ...@lists.macports.org:
>
> To: MacPorts Developers
> Subject: Re: Desolate Condition
> Message-ID:
>
Hi.
I think that the topic installing binaries or not points to a more general
issue, namely public relations. MacPorts could improve a lot on
>
> What if the end of the first sentence was changed to: "ports will be
> installed for only the architecture you're currently running on."?
>
Besides being the most concisely worded, I also find this version to be the
most unambiguous. I think leaving the words "build/built" and "compile" out
of
> It's a tricky thing to state both concisely and accurately because the
> compilation may indeed happen on the user's computer after installation
> is requested. Or it may not. The ambiguity of whether "be compiled" is a
> verb in the passive voice ("the code is being compiled") or a
> descrip
14 matches
Mail list logo
