On Thu, 30 Aug 2007 09:42:03 -0400, Jesse Keating wrote: > On Thu, 30 Aug 2007 09:04:52 -0400 > seth vidal wrote: > > > This doesn't sound terrible to me. If we did provide a list of library > > requirements and application requirements that we define as minimal it > > would be easy to pass that list to yum to resolve and install. > > > > something to think about, anyway. > > Can it be expressed as a comps group though? Does yum comps module > handle that? > > Also keep in mind that part of having the minimal buildroot was so that > when people rebuild packages on their own, they didn't have to hunt > down why their package didn't build right due to silent missing > BuildRequires. That means we start with very little assumptions and > use the BuildRequires to build up exactly what we want around when this > package is built. One used to be able to NOT use mock, but build rpms in an average desktop/workstation installation of Fedora and fill in missing BR consecutively. Dropping core packages from the default target build environment has the effect that one cannot use rpmdev-rmdevelrpms anymore, because it would not uninstall enough packages. It cannot uninstall core packages which are deep in the dep-chain, but which are missing in a new minimal buildroot. Effectively, one would be forced to use mock or lots of scratch-builds in koji to find the new BR. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
