You are not logged in.

#1 2025-04-01 18:24:18

topasiss
Member
Registered: 2022-08-08
Posts: 58

Reproducible builds and non pacman/AUR dependencies

I created a package that has a dependency to another package that is neither in pacman and not yet in the AUR.

I usually do check reproducible builds.

makereprodpkg

produces a download error for the package it depends on when trying to reproduce it.
I tried to give makereprodpkg the built dependency as an argument (like I specify that package for the build in a clean chroot), but there is no such parameter (also not in the repro tool)

I found no information about this situation in combination with reproducible builds.
Neither at the devtools package or the arch wiki, nor in the arch forum.

That makes me think perhaps it doesn't make sense to do a reproducible build when a dependency is not in the official repos.

Is that true? I think with the package that I could theoretically provide - the reproducibility could be checked. If only I could tell the tool to use the dependency that I built.

What do you think about this?

Nest wishes
Tobias

Offline

#2 2025-04-01 18:57:12

mackin_cheese
Member
Registered: 2025-01-07
Posts: 429

Re: Reproducible builds and non pacman/AUR dependencies

You can always just add the dependency into the AUR first, AND THEN proceed with the PKGBUILD of your first package

Online

#3 2025-04-01 21:49:45

Scimmia
Fellow
Registered: 2012-09-01
Posts: 12,580

Re: Reproducible builds and non pacman/AUR dependencies

topasiss wrote:

I usually do check reproducible builds.

Why?

The point of reproducible builds is for someone to be able to reproduce what you're distributing in binary form. It's of no use at all if you're not running a repo, and if you are, you can add the dependency to that repo.

Offline

Board footer

Powered by FluxBB