6:25 p.m.
Hi there,
Is there a proper way to configure autospec to clone *.git directly or is
it mandatory to work with tarballs?
I see "giturl" in options.conf but it seems to prefer to download from url
= ... .tar.gz
Thanks in advance,
6:36 p.m.
On 12/15/2020 10:25 AM, Thiago Maciel wrote:
Hi there,
Is there a proper way to configure autospec to clone *.git directly or is
it mandatory to work with tarballs?
I see "giturl" in options.conf but it seems to prefer to download from url
= ... .tar.gz
by policy choice we only do tar files.
the giturl is only used for other tools and to create changelogs
6:40 p.m.
I see, thank you.
Am Di., 15. Dez. 2020 um 15:36 Uhr schrieb Arjan van de Ven <
arjan(a)linux.intel.com>:
On 12/15/2020 10:25 AM, Thiago Maciel wrote:
> Hi there,
>
> Is there a proper way to configure autospec to clone *.git directly or is
> it mandatory to work with tarballs?
>
> I see "giturl" in options.conf but it seems to prefer to download from
url
> = ... .tar.gz
by policy choice we only do tar files.
the giturl is only used for other tools and to create changelogs
6:57 p.m.
On Tuesday, 15 December 2020 15:40:57 -03 Thiago Maciel wrote:
I see, thank you.
What you can do is point to a tarball of any commit of the Git repository of
your choice, assuming the Git hosting tool on that end supports that (GitLab,
GitHub, cgit do). The important part is that the tarball is fixed to a
specific commit and you will be able to rebuild the RPM package, even if
upstream has moved on.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel DPG Cloud Engineering
7:36 p.m.
What you can do is point to a tarball of any commit of the Git
repository
of
your choice, assuming the Git hosting tool on that end supports that
(GitLab,
GitHub, cgit do). The important part is that the tarball is fixed to a
specific commit and you will be able to rebuild the RPM package, even if
upstream has moved on.
Just what I need! Thank you!
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel DPG Cloud Engineering
313
days inactive
313
days old
4 comments
3 participants
participants (3)
-
Arjan van de Ven -
Thiago Macieira -
Thiago Maciel