On 07/04/2021 08.04, Ryan Schmidt wrote: > 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.
You are right, the list is long, I should have mentioned more details. I discovered that a descending sort order by version causes 2.46.1 and 2.47.0 to show up on top. The development builds all use a lower 0.0.<gitsha1> version number. This way graphviz publishes their tarballs seems rather unique. I have a suspicion that this is not actually the way this GitLab functionality is meant to be used. I would not add functionality for this special case to the gitlab port group unless we discover more projects that use it like this. Rainer
