> Adding a collection of `_root` macros then just seems like a "remedy" for bad
> packaging.
I don't care that much what the prefix is, but this kind of macros was
essential for SCLs, which allowed to have one source package, but the build
configuration changed the destination. In this scenario, there really needs to
be distinction between files from system or from some alternative destination.
And I believe the same applies to Flatpak.
But if you want to have philosophical discussion, then don't forget that
rpmbuild on itself is using this concept, where it is necessary to distinguish
between content from system and from `%{_builddir}` / `%{_buildroot}`
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/721#issuecomment-1810672005
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/721/1810672...@github.com>_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
