DevHeads.net

gcc/gcc-c++ removal from buildroot and more

Hello everyone,

today we finally dropped gcc and gcc-c++ from the buildroot
<https://fedoraproject.org/wiki/Changes/Remove_GCC_from_BuildRoot>. This
made 12 packages go away along with 134MB installed size. This means that
you need to add gcc/gcc-c++ in the BuildRequires (guidelines stated this
for few years but not many were following them).

Also Mark fixed bug today which was pulling in systemd in the buildroot
which was pulling gnutls/libgcrypt/nettle and stuff like that. I don't have
exact numbers what we saved here.

But looking into simple package build for f28 and f29 I see some nice trend.

F28:
DEBUG util.py:439: Install 179 Packages
DEBUG util.py:439: Total download size: 146 M
DEBUG util.py:439: Installed size: 570 M

F29:
DEBUG util.py:439: Install 144 Packages
DEBUG util.py:439: Total download size: 87 M
DEBUG util.py:439: Installed size: 425 M

Comments

Re: gcc/gcc-c++ removal from buildroot and more

By =?UTF-8?Q?Tomas... at 07/09/2018 - 20:02

On Tue, 10 Jul 2018 at 00:17, Igor Gnatenko
< ... at fedoraproject dot org> wrote:
[..]
I'm almost 100% sure that it would be possible to save probably more
by remove generate Requires dependencies using {Lib,Requires}.private
out of .pc files (which are for static linking which is not possible
to use on Fedora because only few devel packages provides static
libraries) than generate 1.7k git changes and remove gcc from minimal
set of packages. Not to mention that similar effect would be possible
to reach by add gcc to glibc-devel and gcc-g++ to libbstdc++-devel
requires.

Just one technical question about forming stub Fedora build env
(because I don't know how it is assembled).
How it is done? Just one time by create minimal build image after add
some set of new updates to official repository than snapshot and clone
such image and use it as base on start build all new packages until
next batch of packages will be pushed to repo used by build systems or
every time which comes new build request such build env is assembled
from scratch?
Using for example btrfs and snapshosts would be possible to start
adding all packages listed in BR instantly. Total storage overhead
will be only ~150MB and nothing would be necessary to download to
assemble such base build env. Cleanup all after finished build .. just
remove shanpshot.

kloczek

Re: gcc/gcc-c++ removal from buildroot and more

By =?UTF-8?Q?Tomas... at 07/09/2018 - 20:08

On Tue, 10 Jul 2018 at 01:02, Tomasz Kłoczko <kloczko. ... at gmail dot com> wrote:
[..]
Yet another question..
Did above storage used sizes are when all packages are installed with
--excludedocs and --define="%_install_langs en,C"?

kloczek