gitlab tags

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

gitlab tags

Jonathan Stickel-5
I am trying to make a port for git-latexdiff. It is hosted on gitlab:

https://gitlab.com/git-latexdiff/git-latexdiff

The project has "tags" which look similar to github's tags (and
releases). I am having trouble specifying the "master_sites" and
"distname" variables for the port in order to download the appropriately
tagged tarball. The download link, e.g.,

https://gitlab.com/git-latexdiff/git-latexdiff/repository/archive.tar.gz?ref=v1.1.4

automatically morphs into a download file of

git-latexdiff-v1.1.4-dc84273afc2e366d6c4f98a07052e651c7d297dd.tar.gz

I've used the github portgroup to mange this with github-hosted ports,
but there is no "gitlab" portgroup.

Any help is appreciated.

Thanks,
Jonathan
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: gitlab tags

Joshua Root-8
On 2017-3-10 02:42 , Jonathan Stickel wrote:

> I am trying to make a port for git-latexdiff. It is hosted on gitlab:
>
> https://gitlab.com/git-latexdiff/git-latexdiff
>
> The project has "tags" which look similar to github's tags (and
> releases). I am having trouble specifying the "master_sites" and
> "distname" variables for the port in order to download the appropriately
> tagged tarball. The download link, e.g.,
>
> https://gitlab.com/git-latexdiff/git-latexdiff/repository/archive.tar.gz?ref=v1.1.4
>
>
> automatically morphs into a download file of
>
> git-latexdiff-v1.1.4-dc84273afc2e366d6c4f98a07052e651c7d297dd.tar.gz
>
> I've used the github portgroup to mange this with github-hosted ports,
> but there is no "gitlab" portgroup.
>
> Any help is appreciated.

I don't know about Gitlab specifically, but if they really don't have
any other way to download the source, you can use the ?dummy= trick:

<https://trac.macports.org/wiki/PortfileRecipes#fetchwithgetparams>

- Josh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: gitlab tags

Mojca Miklavec-2
In reply to this post by Jonathan Stickel-5
On 9 March 2017 at 16:42, Jonathan Stickel <[hidden email]> wrote:

> I am trying to make a port for git-latexdiff. It is hosted on gitlab:
>
> https://gitlab.com/git-latexdiff/git-latexdiff
>
> The project has "tags" which look similar to github's tags (and releases). I
> am having trouble specifying the "master_sites" and "distname" variables for
> the port in order to download the appropriately tagged tarball. The download
> link, e.g.,
>
> https://gitlab.com/git-latexdiff/git-latexdiff/repository/archive.tar.gz?ref=v1.1.4
>
> automatically morphs into a download file of
>
> git-latexdiff-v1.1.4-dc84273afc2e366d6c4f98a07052e651c7d297dd.tar.gz
>
> I've used the github portgroup to mange this with github-hosted ports, but
> there is no "gitlab" portgroup.

I would say that we should create a PortGroup for GitLab.

Mojca
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: gitlab tags

Jonathan Stickel-5
In reply to this post by Joshua Root-8
On 3/9/17 10:11 , Joshua Root wrote:

> On 2017-3-10 02:42 , Jonathan Stickel wrote:
>> I am trying to make a port for git-latexdiff. It is hosted on gitlab:
>>
>> https://gitlab.com/git-latexdiff/git-latexdiff
>>
>> The project has "tags" which look similar to github's tags (and
>> releases). I am having trouble specifying the "master_sites" and
>> "distname" variables for the port in order to download the appropriately
>> tagged tarball. The download link, e.g.,
>>
>> https://gitlab.com/git-latexdiff/git-latexdiff/repository/archive.tar.gz?ref=v1.1.4
>>
>>
>>
>> automatically morphs into a download file of
>>
>> git-latexdiff-v1.1.4-dc84273afc2e366d6c4f98a07052e651c7d297dd.tar.gz
>>
>> I've used the github portgroup to mange this with github-hosted ports,
>> but there is no "gitlab" portgroup.
>>
>> Any help is appreciated.
>
> I don't know about Gitlab specifically, but if they really don't have
> any other way to download the source, you can use the ?dummy= trick:
>
> <https://trac.macports.org/wiki/PortfileRecipes#fetchwithgetparams>
>
> - Josh

Thanks, appending "&dummy=" worked in this case.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: gitlab tags

Jonathan Stickel-5
In reply to this post by Mojca Miklavec-2
On 3/9/17 11:26 , Mojca Miklavec wrote:

> On 9 March 2017 at 16:42, Jonathan Stickel <[hidden email]> wrote:
>> I am trying to make a port for git-latexdiff. It is hosted on gitlab:
>>
>> https://gitlab.com/git-latexdiff/git-latexdiff
>>
>> The project has "tags" which look similar to github's tags (and releases). I
>> am having trouble specifying the "master_sites" and "distname" variables for
>> the port in order to download the appropriately tagged tarball. The download
>> link, e.g.,
>>
>> https://gitlab.com/git-latexdiff/git-latexdiff/repository/archive.tar.gz?ref=v1.1.4
>>
>> automatically morphs into a download file of
>>
>> git-latexdiff-v1.1.4-dc84273afc2e366d6c4f98a07052e651c7d297dd.tar.gz
>>
>> I've used the github portgroup to mange this with github-hosted ports, but
>> there is no "gitlab" portgroup.
>
> I would say that we should create a PortGroup for GitLab.
>
> Mojca
>

Sure, that would be helpful, but it looks like only 3 ports are
currently associated with gitlab:

[...]/release/tarballs/ports $ grep -Ri "gitlab" .
./archivers/libaec/Portfile:homepage
https://gitlab.dkrz.de/k202009/libaec
./gnome/uhttpmock/Portfile:homepage
https://gitlab.com/groups/${name}
./kde/kcm-baloo-advanced/Portfile:git.url
https://gitlab.com/baloo-kcmadv/baloo-kcmadv.git
./kde/kcm-baloo-advanced/Portfile:homepage
https://gitlab.com/baloo-kcmadv/baloo-kcmadv

So probably not worth the work at the moment.

Jonathan
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: gitlab tags

Mojca Miklavec-2
On 9 March 2017 at 20:34, Jonathan Stickel wrote:
> On 3/9/17 11:26 , Mojca Miklavec wrote:
>>
>> I would say that we should create a PortGroup for GitLab.
>
> Sure, that would be helpful, but it looks like only 3 ports are currently
> associated with gitlab:
>
> So probably not worth the work at the moment.

It doesn't matter if that contributes (a lot) to simplicity of the Portfiles.

Mojca
Loading...