@pmatilai commented on this pull request.
> @@ -1352,5 +1352,16 @@ end
end
}
+# buildsystem defaults
+%buildsystem_default_prep() %autosetup -p1
Oh, another point regarding this: this will allow declaratively changing %prep
behavior too, eg `BuildOption(prep): -n %{name}`. That wont wo
This would be another rather critical fix to include:
https://github.com/rpm-software-management/rpm/pull/2797
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2791#issuecomment-1833630593
You are receiving this because you are subscribed
@pmatilai pushed 2 commits.
fabff3f0a0453e30e5273940bfc3876494449a3d Never use current user info or file
ownership during build
152057cb2b9a4a096e137bd2840512c518805984 Make rpmug*() properly internal to
librpm now that we can
--
View it on GitHub:
https://github.com/rpm-software-management/
@pmatilai pushed 1 commit.
11a2eb40ffdb86ccd261b2694f4099ea6acbd41e Make rpmug*() properly internal to
librpm now that we can
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2797/files/6a64145bde1ce782b56d0f60a0951d4a7a7e8327..11a2eb40ffdb86ccd261b2694f4099ea6acbd41e
There's no situation where rpmbuild should use uid/gid from either the
filesystem or current user. The former made sense in the pre-historic times
before Buildroot was a thing, but in the last 20+ years that's always the
wrong thing to do. Always. The only user/group info rpm can legitimately us
