Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 7 Mar 2021 00:35:45 -0800 (PST)
From:      "Dan Mahoney (Gushi)" <danm@prime.gushi.org>
To:        Kevin Oberman <rkoberman@gmail.com>
Cc:        Hiroo Ono <hiroo.ono@gmail.com>, FreeBSD Ports ML <freebsd-ports@freebsd.org>
Subject:   Re: Problems with updating a port due to top directory in tarball
Message-ID:  <85195dbb-d39c-8253-5031-aa5defb0ad3c@prime.gushi.org>
In-Reply-To: <CAN6yY1sCSAJ65E51X7bSLYS0uQptauV%2B=SNU1dQ8q-m1NnVvZQ@mail.gmail.com>
References:  <CAN6yY1tb=b7JRuG-YbYV9Unw%2BST998xbGEEiE6HjOrN3k-k3Pw@mail.gmail.com> <0538558a-880e-415d-8499-5b7ea05212e3@gmail.com> <CAN6yY1sCSAJ65E51X7bSLYS0uQptauV%2B=SNU1dQ8q-m1NnVvZQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 6 Mar 2021, Kevin Oberman wrote:

> On Wed, Mar 3, 2021 at 10:15 PM Hiroo Ono <hiroo.ono@gmail.com> wrote:
>
>>
>> On 2021=E5=B9=B43=E6=9C=884=E6=97=A5=E6=9C=A8=E6=9B=9C=E6=97=A5 9=E6=99=
=8200=E5=88=8632=E7=A7=92 JST, Kevin Oberman wrote:
>>> I'm trying to update a port I maintain. Since I last updated, it moved
>> from
>>> ISC to github and it uses unusual naming conventions.
>>>
>>> The distfile is "irrtoolset/archive/release-5.1.3.tar.gz". I can work
>>> around this with a DIST_SUBDIR and DISTNAME, but when the extract takes
>>> place,  the top directory in the tarball is "irrtoolset-release-5.1.3".
>>> Since this is not expected, patch fails.
>>
>> If it is same as what is tagged as "release-5.1.3",
>>
>> DISTVERSIONPREFIX=3D      release-
>> DISTVERSION=3D    5.1.3
>> USE_GITHUB=3D     yes
>> GH_ACCOUNT=3D     irrtoolset
>> GH_PROJECT=3D     irrtoolset
>>
>> should work.
>> cf.
>>
>> https://docs.freebsd.org/en_US.ISO8859-1/books/porters-handbook/makefile=
-distfiles.html#makefile-master_sites-github-description
>>
>> Thanks you very much! The update to the port has been submitted and is
> awaiting a committer. Looking at the Porter's Handbook, I now understand
> how it works, but it would have taken a VERY long time to figure it all o=
ut
> without your help! (Might have taken until the heat death of the universe=
=2E)

I also was hitting some issues with this for opendmarc, which recently=20
moved from Sourceforge to Github.  Well, moved a while ago but put out its=
=20
first github-exclusive release recently.

For some of the process, portsfiles just plain didn't try to fetch.  Even=
=20
when I copied the relevant variables verbatim from another port.

Despite having the porter's handbook open lots, there were many things I=20
had to just go read the files in /usr/ports/Mk to figure out.

There could definitely be more recipes.  One example: how to correctly=20
handle a port that uses an RPM.  Or multiple RPMs.

--=20

--------Dan Mahoney--------
Techie,  Sysadmin,  WebGeek
Gushi on efnet/undernet IRC
FB:  fb.com/DanielMahoneyIV
LI:   linkedin.com/in/gushi
Site:  http://www.gushi.org
---------------------------



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85195dbb-d39c-8253-5031-aa5defb0ad3c>