Re: map download link to distname
On Apr 6, 2021, at 10:44, Rainer Müller wrote: > On 06/04/2021 01.39, Ryan Schmidt wrote: >> Regarding the specific download link you mentioned, >> https://gitlab.com/graphviz/graphviz/-/package_files/8183714/download, I see >> that link on the graphviz web site at >> http://www.graphviz.org/download/source/ but I don't know where they got it. >> I can't find that link within their gitlab site. I don't know whether that >> is what in github parlance would be called a release download or whether it >> is yet another different type of download which is specific to gitlab for >> which there is not an equivalent within github. > > This is also the first time I have seen this. Apparently graphviz publishes > this > as a "package" on GitLab, which contains artifacts archived after CI pipeline > runs. You can locate the resulting files via the "Package Registry" section in > the menu. > > https://gitlab.com/graphviz/graphviz/-/packages/1365772 Yes, I found "Package Registry" in the GitLab menu, but all I found there was tons of development version artifacts. I could not see a way to show stable version artifacts.
Re: map download link to distname
On 4/6/21 09:45, Rainer Müller wrote:
On 06/04/2021 16.38, Jonathan Stickel wrote:
On 4/5/21 17:39, Ryan Schmidt wrote:
master_siteshttps://gitlab.com/graphviz/graphviz/-/package_files/${package_id}/download?dummy=
Thank you, this is the piece that I was missing. I was not familiar with URL
query strings. Maybe this is something useful to include in
https://trac.macports.org/wiki/CommittersTipsAndTricks
? I can add something to the page and submit for review.
It is explained on the PortfileRecipes page that Ryan already linked earlier:
https://trac.macports.org/wiki/PortfileRecipes#fetchwithgetparams
One problem is that this page is not visible enough. The documents for new
project members should have a link to that. I could not find any reference from
the guide either...
Ah, and now I see Ryan gave me that link previously, but I didn't read
it carefully enough to understand it--sorry about that. I suppose I need
to better familiarize myself with the PortfileRecipes wiki.
Re: What's our audience - and how do we serve them best
Hi Bjarne, > On Apr 5, 2021, at 4:16 PM, Bjarne D Mathiesen > wrote: > > As I see it, we've got several problems/issues : > > 2) how does one use macports in daily life ? > we've got a section : > https://trac.macports.org/wiki/howto > that we collectively ought try to promote better & bring up-to-date > & yes - I'm guilty here as the sections I've authored haven't been > kept updated :-( In my defence, I didn't experience much ethusiasm / > support for my efforts, so I more-or-less gave up. > There was/is a lot of negative put downs : > - "that's not recommended" > - "we don't do it that way" > instead of saying : "that's interesting !? why does he find it > necessary doing it that way ?!? could we incorporate his ideas & > improve upon them ?!?" > and generally no feedback at all. We do have standards that aren’t always documented. Those hopefully get communicated with PR reviews. No one on the project is negative IMHO but I agree we aren’t always overly positive. If feedback is not followed then PRs tend to not get accepted. Please don’t take it personally. Also sometimes no one has gotten to it. Successful contributors who eventually become committers are the ones who are persistant self starters and follow our established standards. People who are knowledgable and contribute a lot of time and code can establish new standards. > 4) Public Relations > As has been stated elsewhere, almost nobody knows about macports. > Everybody references brew. I've just read a book on how to work with > Terminal : > https://www.apress.com/gp/book/9781484261705 > and the go-to package manager is brew. Some of the stuff mentioned > installed with brew isn't present in macports, but those are minor > issues. > A course of action ought to be, that when one of us sees brew > referenced as !the! way to install something, then to take contact > and get the site to reference macports too. Yes it’s safe to say that we don’t have anyone on the project who actively promotes it. We tend to simply fix and update ports and not be political or grandstanding about it. In the past, I have asked a few upstream projects to mention Macports as a method to install their project and given them instructions to use. Cheers! Frank
Re: map download link to distname
On 06/04/2021 16.38, Jonathan Stickel wrote:
> On 4/5/21 17:39, Ryan Schmidt wrote:
>> master_siteshttps://gitlab.com/graphviz/graphviz/-/package_files/${package_id}/download?dummy=
>>
>
> Thank you, this is the piece that I was missing. I was not familiar with URL
> query strings. Maybe this is something useful to include in
>
> https://trac.macports.org/wiki/CommittersTipsAndTricks
>
> ? I can add something to the page and submit for review.
It is explained on the PortfileRecipes page that Ryan already linked earlier:
https://trac.macports.org/wiki/PortfileRecipes#fetchwithgetparams
One problem is that this page is not visible enough. The documents for new
project members should have a link to that. I could not find any reference from
the guide either...
Rainer
Re: map download link to distname
On 06/04/2021 01.39, Ryan Schmidt wrote: > Regarding the specific download link you mentioned, > https://gitlab.com/graphviz/graphviz/-/package_files/8183714/download, I see > that link on the graphviz web site at > http://www.graphviz.org/download/source/ but I don't know where they got it. > I can't find that link within their gitlab site. I don't know whether that is > what in github parlance would be called a release download or whether it is > yet another different type of download which is specific to gitlab for which > there is not an equivalent within github. This is also the first time I have seen this. Apparently graphviz publishes this as a "package" on GitLab, which contains artifacts archived after CI pipeline runs. You can locate the resulting files via the "Package Registry" section in the menu. https://gitlab.com/graphviz/graphviz/-/packages/1365772 Rainer
Re: map download link to distname
On 4/5/21 17:39, Ryan Schmidt wrote:
master_siteshttps://gitlab.com/graphviz/graphviz/-/package_files/${package_id}/download?dummy=
Thank you, this is the piece that I was missing. I was not familiar with
URL query strings. Maybe this is something useful to include in
https://trac.macports.org/wiki/CommittersTipsAndTricks
? I can add something to the page and submit for review.
Re: What's our audience - and how do we serve them best
On Apr 5, 2021, at 20:42, Bjarne D Mathiesen wrote: > 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 upstream >>> to fix them instead of finding (temporary) workarounds. Try looking for >>> "php80-imagick" in the threads. >> >> The php imagick module is not compatible with php 8 or later. It is not our >> job to make it so. Other than MacPorts base and supporting software, we do >> not develop the software. We provide software that has been developed by >> others and what the other developers choose to support or not is out of our >> control. >> >> Anyone is welcome to contribute e.g. to the upstream php imagick project to >> make it php 8+ compatible. When that happens, we'll update to the new >> version of MacPorts. > > I fully understand that macports as such doesn't have the job of fixing > this situation upstream - and that's also not what I'm asking for / > proposing. I'm proposing something like when a port is deprecated so one > gets a note about the situation. MacPorts does have a "deprecated" portgroup which portfile authors can include into their ports to indicate various states of unsupportedness. > We are back to who the audience is : > > If it's "nerds" -or- "linux refugees" all is good and well - they are > able to find the fix/workaround on their own (as I did). > > But if we want to cater to newbies, Certainly I would like to cater to everyone. > we'll (IMHO) have to provide some > way to tell them : > - why isn't php80-imagick available > - what's the (possible) workaround I'm not sure what you're proposing we do. The reason why any port doesn't exist is that is hasn't been or cannot be created. The workaround is to create and submit the port yourself, or see if someone has already submitted it in a PR or ticket, or use a different port, or use software outside of MacPorts, or figure out why the port can't be created and work toward fixing that. > And php80-imagick is only used as an example here. Certainly. If you have other examples I can try to respond to those as well. But I'm not sure what general purpose answer you're expecting to receive.
