Just whipped this up this arvo. I plan to test it more downstream here in the morning.. but wanted to get something up incase either anyone is interested or if there is a better way.

I guess I should probably look to see if there is any testing in the repo and add some tests. But first dinner time!

I wonder, why do you need tokens to download GitLab sources? Are you handling private repositories?

Yeah, we have a private gitlab instance downstream with private repos. And
changing them to public is not an option.
I'm reworking/modernising the build system here, but some specs point to
public repos, some on github, but there are quite alot of specs whose main
sources are in private repos.
And this allows me to optionally pass in the token header when using spec
tool to pull the sources in the latter.

Matt

On Tue, 20 June 2023, 4:55 am Fabio Valentini, pagure@pagure.io wrote:

decathorpe commented on the pull-request: Add --header option to spectool that you are following:
I wonder, why do you need tokens to download GitLab sources? Are you handling private repositories?

To reply, visit the link below or just reply to this email
https://pagure.io/rpmdevtools/pull-request/112

I guess for completeness I should make this:

headers=headers

too.

Please change this to http-header

Sure can, I was just matching curl's, but yeah header alone could be confusing, great thought!

Is the anything else needed or suggested for this patch? We're building it and using downstream in our env now.. It would be much nicer if one day we didn't have to ;)

:thumbsup: