Interested in something like this for openSUSE. We already have something
comparable called `_buildenv` (XML) e.g. in
https://build.opensuse.org/package/binaries/openSUSE:Factory/bash/standard -
but that is created on the obs_worker level.
[ArchLinux](https://archlinux.org/pacman/BUILDINFO.5.html) seems to have their
own format with = as delimiter.
In most places, the buildinfo files can probably be handled as opaque files and
just things like source,binary,version would be interesting outside. That is
not hard to extract in either format, so there is no strong reason to follow
Debian here.
OTOH, this is not a .spec file, but just another output from the build process,
similar to the build log, so it does not need to follow rpm conventions either.
So from my view, using either the Debian or ArchLinux (marshalling) format has
some advantage over making up a third format.
Though, I would not keep confusing Debianisms in keys that will not be
meaningful outside of the respective distribution.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1532#issuecomment-942694178
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
