Re: Publicizing MacPorts

Hi > Am 19.04.2021 um 16:47 schrieb Karl-Michael Schindler > : > > I intend to do so, probably to a limited extend only. As a first step, I have > checked the upstream download pages of our top ten downloads. Less than 5 of > them mention macports properly. My next steps is to write to them.

Re: Publicizing MacPorts [installation]

A script that’ll download the installer pkg and then run the installer cli command i.e. something like cd ~/Downloads curl -OL /url/of/installer.pkg sudo installer -pkg installer.pkg -target / > On May 23, 2021, at 12:58 PM, Joshua Root > wrote: > > On 2021-5-23

Re: Publicizing MacPorts [installation]

On 2021-5-23 20:40 , Artem Loenko via macports-dev wrote: If you ask me, `curl | sh` is a better option than `sudo make install`. Even if we compare them both as anti-patterns. If you haven't done any verification of the integrity of what you're installing, 'make install' is certainly also a

Re: Publicizing MacPorts

> On 22 May 2021, at 13:21, Artem Loenko via macports-dev > wrote: > > Hello there, > > I agree with all the points about publicity (blog posts, Twitter, etc.). But > I want to share the opinion on MacPorts from a (power?) user who is aware of > the tool and “deep in my heart” believe that

Re: Publicizing MacPorts [installation]

> On Sat, May 22, 2021 at 1:35 PM Ken Cunningham > wrote: > > cd /tmp > git clone -b release-2.7 https://github.com/macports/macports-base.git > cd macports-base > ./configure && make && sudo make install > > and then add to the $PATH as usual If you ask me, `curl | sh` is a better option than

Re: Publicizing MacPorts [installation]

Joshua Root wrote: > I think the best thing we could do to facilitate one-liner command line > installation is set up a redirect so you can download the latest binary > installer for your OS version without having to construct its > not-so-easy-to-derive name yourself. It would then be simple to

Re: Publicizing MacPorts [installation]

Joshua Root wrote: > On 2021-5-23 03:12 , Bjarne D Mathiesen wrote: >> >> >> Artem Loenko wrote: >>> Yes, thanks for the tips! I am pretty sure that it is possible to >>> automate it one way or another. But my point is that it would be >>> helpful to have a one-liner to install MacPorts and

Re: Publicizing MacPorts [installation]

On Sat, May 22, 2021 at 1:35 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > > Yes, thanks for the tips! I am pretty sure that it is possible to automate >> it one way or another. But my point is that it would be helpful to have a >> one-liner to install MacPorts and maintain it as a

Re: Publicizing MacPorts [installation]

On 2021-5-23 03:12 , Bjarne D Mathiesen wrote: Artem Loenko wrote: Yes, thanks for the tips! I am pretty sure that it is possible to automate it one way or another. But my point is that it would be helpful to have a one-liner to install MacPorts and maintain it as a part of the main

Re: Publicizing MacPorts [installation]

> Yes, thanks for the tips! I am pretty sure that it is possible to automate it > one way or another. But my point is that it would be helpful to have a > one-liner to install MacPorts and maintain it as a part of the main > repository. This was of course suggested years ago as well, when

Re: Publicizing MacPorts [installation]

Artem Loenko wrote: > Yes, thanks for the tips! I am pretty sure that it is possible to automate it > one way or another. But my point is that it would be helpful to have a > one-liner to install MacPorts and maintain it as a part of the main > repository. > I'm 90% there there with this :

Re: Publicizing MacPorts [installation]

Yes, thanks for the tips! I am pretty sure that it is possible to automate it one way or another. But my point is that it would be helpful to have a one-liner to install MacPorts and maintain it as a part of the main repository. Regards, Artem > On 22 May 2021, at 15:01, Bjarne D Mathiesen

Re: Publicizing MacPorts [installation]

Joshua Root wrote: > On 2021-5-22 23:17 , Bjarne D Mathiesen wrote: >> >> My own installation script looks something like this : >> >> #!/usr/bin/env bash >> >> prefix=$(1:-'/opt/local') >> version=${2:-'2.7.0'} > > I you want to automatically use the latest version, it can be found in >

Re: Publicizing MacPorts [installation]

On 2021-5-22 23:17 , Bjarne D Mathiesen wrote: My own installation script looks something like this : #!/usr/bin/env bash prefix=$(1:-'/opt/local') version=${2:-'2.7.0'} I you want to automatically use the latest version, it can be found in

Re: Publicizing MacPorts [installation]

Artem Loenko via macports-dev wrote: > INSTALLATION > > The current process is described well[1], but it is almost impossible to > automate it. For a tool that supposes to be a CLI to manage everything, > this is a disadvantage for me. Yes, I can install MacPorts from the > command-line with

Re: Publicizing MacPorts [bundles]

Artem Loenko via macports-dev wrote: > BUNDLES > > Homebrew supports bundles[3] where you can list all the software you use > and install it with a simple `brew bundle` command. It is a convenient > way to track a list of software you use, migrate between machines or set > up remote hardware

Re: Publicizing MacPorts

Hello there, I agree with all the points about publicity (blog posts, Twitter, etc.). But I want to share the opinion on MacPorts from a (power?) user who is aware of the tool and “deep in my heart” believe that MacPorts is a better option than, for example, Homebrew. INSTALLATION The

Re: Publicizing MacPorts

I’m not a MacPorts core maintainer or anything, nor am I a PR expert, but (for various reasons) I happen to interact with a lot of users who are curious about macOS package managers. Here’s a couple of takeaways I have from those conversations, as well as my thoughts on what MacPorts could do

Re: Publicizing MacPorts

Georges Martin wrote: > - What if a port is not building on M1 because upstream is not ready yet? > (libffi, openjdk16, ghc comes to mind) The openjdk16 port in MacPorts indeed doesn’t support arm64 yet, because AdoptOpenJDK hasn’t released their arm64 version for macOS yet. I have added

Re: Publicizing MacPorts

On Sat, 24 Apr 2021 at 13:04, Georges Martin wrote: > > Le 22 avr. 2021 à 17:46, Steven Smith a écrit : > > Another reason major news like M1 support must be announced. > > > May I ask: how do we *define* "M1 support" in MacPorts? What are the > *metrics* used to support that statement? > > -

Re: Publicizing MacPorts

Hi, > On 24 Apr 2021, at 12:04 pm, Georges Martin wrote: > >> Le 22 avr. 2021 à 17:46, Steven Smith > > a écrit : >> >> Another reason major news like M1 support must be announced. > > > May I ask: how do we *define* "M1 support" in MacPorts? What are the >

Re: Publicizing MacPorts

> Le 22 avr. 2021 à 17:46, Steven Smith a écrit : > > Another reason major news like M1 support must be announced. May I ask: how do we *define* "M1 support" in MacPorts? What are the *metrics* used to support that statement? - How does the MacPorts base "support the M1"? (I know I had to

Publicizing MacPorts

 > > Ironically, MacPorts is claimed to have "initial or beta support" for > Apple silicon on https://isapplesiliconready.com/ Another reason major news like M1 support must be announced. As a volunteer, I could quickly post a correction, but in doing so this website reasonably asks for a

Re: Publicizing MacPorts

On Mon, Apr 19, 2021 at 01:24:51PM +0200, Mojca Miklavec wrote: On Mon, 19 Apr 2021 at 12:45, Steven Smith wrote: If a comparable announcement to this was made for MacPorts, I missed it:

Re: Publicizing MacPorts

On Wed, Apr 21, 2021 at 10:42 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > A set of pages with some screenshots of some of the cool GUI software and > games, like SNAP has for Ubuntu. To piggyback off Ken's statement, as a part of the modernization efforts for the website, it

Re: Publicizing MacPorts

various people have come along with some good ideas over the five years I’ve been around. A set of pages with some screenshots of some of the cool GUI software and games, like SNAP has for Ubuntu. A rewrite of the very old and dated and cobwebby website. To be honest — these people in the

Re: Publicizing MacPorts

> MacPorts faces is that it has an image of being “old and dead”, especially > compared to vibrant alternatives such as Homebrew. This is the issue. If you don’t tell your own story, others will. MacPorts is not telling its own story. Saagar’s consequent suggestions are also excellent:

Re: Publicizing MacPorts

> If you pledge to handle this kind of marketing, I would have no problem to > hand out an @macports.org address for that. Thank you for the confidence. There are posts I could and would write about the utility specific ports that are only available from MacPorts. But I’m honestly not the

Re: Publicizing MacPorts

On 4/19/21 3:54 PM, Craig Treleaven wrote: > >> On Apr 19, 2021, at 2:51 PM, Jason Liu > > wrote: >> >> On Mon, Apr 19, 2021 at 1:25 PM Craig Treleaven > > wrote: >> >> Also, why should we consider that MacPorts is in competition with

Re: Publicizing MacPorts

On 20/04/2021 12.40, Steven Smith wrote: That’s begging the question of an effective communications strategy. A distributed model of random volunteers is perfect for aggregating git commits. It’s highly ineffective at communicating important news from that organization. If MacPorts wants to

Re: Publicizing MacPorts

On Tue, 20 Apr 2021 at 12:41, Steven Smith wrote: > > > What Ryan is trying to say is that "MacPorts" is in fact just a set of > > random volunteer contributors > > That’s begging the question of an effective communications strategy. A > distributed model of random volunteers is perfect for

Re: Publicizing MacPorts

> What Ryan is trying to say is that "MacPorts" is in fact just a set of > random volunteer contributors That’s begging the question of an effective communications strategy. A distributed model of random volunteers is perfect for aggregating git commits. It’s highly ineffective at communicating

Re: Publicizing MacPorts

On Mon, 19 Apr 2021 at 15:14, Steven Smith wrote: > > > If you have contacts to tech reporters, please use them. I don't have any. > > If Ars Technica or any other news site wants to cover MacPorts, they can do > > that any time. > > This is the wrong attitude. > > MacPorts must tell them, not

Re: Publicizing MacPorts

Done: https://github.com/macports/macports-ports/pull/10726 > Le 19 avr. 2021 à 23:46, Clemens Lang a écrit : > > Hi, > > On Mon, Apr 19, 2021 at 07:58:02PM +0200, Georges Martin wrote: >> Speaking of the PR checklist, the "Tested On" section could include the >> architecture name: >> >>

Re: Publicizing MacPorts

Hi, On Mon, Apr 19, 2021 at 07:58:02PM +0200, Georges Martin wrote: > Speaking of the PR checklist, the "Tested On" section could include the > architecture name: > > echo "macOS $(sw_vers -productVersion) $(sw_vers -buildVersion) on > $(uname -m)" > > As I'm now testing both on x86_64

Re: Publicizing MacPorts

> On Apr 19, 2021, at 2:51 PM, Jason Liu wrote: > > On Mon, Apr 19, 2021 at 1:25 PM Craig Treleaven > wrote: > Also, why should we consider that MacPorts is in competition with Homebrew? > Both MacPorts and Homebrew seem to have a sufficient number of

Re: Publicizing MacPorts

leaven wrote: > > On Apr 19, 2021, at 10:47 AM, Karl-Michael Schindler < > karl-michael.schind...@physik.uni-halle.de> wrote: > > > > Am 19.04.2021 um 14:00 schrieb macports-dev-requ...@lists.macports.org: > >> > >> Date: Mon, 19 Apr 2021 13:24:51 +0200 > >

Re: Publicizing MacPorts

It would be very helpful for new impressions of Macports, if the ports website could be fixed to properly show current port status. This problem has been lingering for months now: https://github.com/macports/macports-webapp/issues/273 On Mon, Apr 19, 2021 at 9:59 AM Dave Allured - NOAA

Re: Publicizing MacPorts

> On Apr 19, 2021, at 10:47 AM, Karl-Michael Schindler > wrote: > > Am 19.04.2021 um 14:00 schrieb macports-dev-requ...@lists.macports.org: >> >> Date: Mon, 19 Apr 2021 13:24:51 +0200 >> From: Mojca Miklavec >> Subject: Re: Publicizing MacPorts >> Me

Re: Publicizing MacPorts

Here are a few ideas. How many M1 ports are working on Macports? How many on Homebrew and other competitors? How long ago did Macports start to have working M1 ports? Are there any noteworthy M1 ports that are working on Macports, but not on Homebrew? On Mon, Apr 19, 2021 at 8:47 AM Rainer

Re: Publicizing MacPorts

Am 19.04.2021 um 14:00 schrieb macports-dev-requ...@lists.macports.org: > > Date: Mon, 19 Apr 2021 13:24:51 +0200 > From: Mojca Miklavec > Subject: Re: Publicizing MacPorts > Message-ID: > > Content-Type: text/plain; charset="UTF-8" > > We should probab

Re: Publicizing MacPorts

On 19/04/2021 15.14, Steven Smith wrote: If you have contacts to tech reporters, please use them. I don't have any. If Ars Technica or any other news site wants to cover MacPorts, they can do that any time. This is the wrong attitude. MacPorts must tell them, not some random

Re: Publicizing MacPorts

> If you have contacts to tech reporters, please use them. I don't have any. If > Ars Technica or any other news site wants to cover MacPorts, they can do that > any time. This is the wrong attitude. MacPorts must tell them, not some random user/contributer like me. Everyone has tech

Re: Publicizing MacPorts

> We never made any announcement since it basically "worked from day 1" Then that’s the announcement! No one will know this stuff if MacPorts doesn’t tell them. There must be one or two regular broadcast channels: perhaps a blog on your website for major announcer, and Twitter feed for

Re: Publicizing MacPorts

On 19/04/2021 12.45, Steven Smith wrote: "Champion" how? "MacPorts should be making [the case]" how? The same way everyone else does: make noise, push news, promote, let the tech reporters know. Follow the Woody Allen rule for success. If a comparable announcement to this was made for

Re: Publicizing MacPorts

On Mon, 19 Apr 2021 at 12:45, Steven Smith wrote: > > If a comparable announcement to this was made for MacPorts, I missed it: > > https://arstechnica.com/gadgets/2021/02/mac-utility-homebrew-finally-gets-native-apple-silicon-and-m1-support/ We never made any announcement since it basically

Re: Publicizing MacPorts

On Apr 18, 2021, at 07:28, Steven Smith wrote: >>> I completely agree that Homebrew is currently winning at publicity. >> >> What should the MacPorts community be doing do publicize MacPorts better? > > The new M1 architecture is a perfect opportunity to champion MacPorts’s > strengths: >

Publicizing MacPorts

>> I completely agree that Homebrew is currently winning at publicity. > > What should the MacPorts community be doing do publicize MacPorts better? The new M1 architecture is a perfect opportunity to champion MacPorts’s strengths: • Strong emphasis on binaries built from source code, often