On Tue, Dec 16, 2014 at 02:19:13PM +0100, Jan Engelhardt wrote:
On Tuesday 2014-12-16 13:33, Michael Schroeder wrote:
because Preinstall is interpreted as a list of packages rather than an additional source of dependencies.
Not sure if any of the above can be improved to make it easier to support a BuildRequires of a non-system gcc. Michael?
Yes, I think it's currently not possible to mess with the preinstalls on a per-packages basis. So you can't get rid of libgcc_s1 without changing the project config.
In fact, if Preinstall were to be a solvable, we would not even need Preinstall: libgcc_s1, but could source things through Preinstall/Requires: somethingelse.
You mean we should run the dependency solver for some small "preinstall" set, so that we don't need to list all libraries? We could do that, but we also need a way to change the list from a specfile. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org