One thing to keep in mind here is that we'll be getting rid of a shared
BUILDROOT. I've always wondered what the purpose of that (or the shared
`%_topdir` workspace in general) was, but I can think of one use case:
You wish to deploy a common set of packages and/or configuration (a *suite*) to
a number of hosts in your organization. You want that suite to be managed and
updated "atomically" as a whole, and ideally distributed as a single binary RPM
without additional dependencies. This is where the shared RPM workspace comes
into play! You simply build those individual packages locally one by one, and
finally build the "meta" package that just packages the resulting BUILDROOT.
Basically, this is what container images are in the modern world. I don't think
the above use case is very common (or real at all) but I can imagine that being
one of the motivations behind the shared workspace back then.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2885#issuecomment-1957030714
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/2885/c1957030...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
