[gentoo-musl] Can't install Gentoo musl x86; Please ship working git+layman

["Walter Dnes" <waltdnes@waltdnes.org>]

[-- Attachment #1: Type: text/plain, Size: 2823 bytes --]

  Quickie analysis... I followed the instructions in the HOWTO file at
http://distfiles.gentoo.org/experimental/x86/musl/HOWTO probably the
problem.  It may have been possible to build git and layman against the
standard portage tree, before activating layman when
stage3-i686-musl-vanilla-20180304.tar.bz2 shipped.  That's not the case
now.  The portage tree is constantly changing

  I followed the instructions, with a standard chroot from the minimal
install ISO.  Things break down at Step 3 of the HOWTO.  Emerging
layman+git wants to build 65 packages!!!  This runs into into the
problems noted in Step 5 (what happens if you don't activate layman
before emerging world).  Chicken+egg problem... I can't build layman+git
without having functioning layman+git to set up the overlay first.
Given that layman and git are crucial to installing the libmusl distro,
please ship the stage3 tarball with a working layman+git.  It may have
worked when the stage3 tarball was released, but the portage tree is
constantly changing.

  I admit that I might have goofed somewhere.  But let's just say that
I've done a lot of Gentoo installs, going back to the days of "stage 1",
and I think I've followed the HOWTO properly.  For diagnostics, see the
attachment.

OUTPUT 1 is the first attempt to emerge layman+git.  Portage says to add
">=dev-libs/openssl-1.0.2n -bindist" into /etc/portage/package.use

OUTPUT 2 is what happens after adding the line to package.use.

  I did try unmasking+keywording as per OUTPUT 2.  You do not want to
see "OUTPUT 3".  Even with --keep-going it eventually died and failed
with multiple packages not building.

  A couple of additional comments...

1) It would be nice to have app-portage/cpuid2cpuflags shipped as part
of this (and all) stage3 tarballs.  Many installs require an
"emerge -e @world" step, so lets have the cpu flags set right when it's
run.

2) "eselect news list" gives stuff going back to 2013!  We're on GCC
6.4.0 already, so why worry about notices for GCC 4 and 5?  The first 9
items below can be dropped from the tarball.

(chroot) livecd / # eselect news list
News items:
  [1]   N  2013-09-27  Separate /usr on Linux requires initramfs
  [2]   N  2014-06-15  GCC 4.8.3 defaults to -fstack-protector
  [3]   N  2014-10-22  Upgrading to musl 1.1.5
  [4]   N  2014-10-26  GCC 4.7 Introduced the New C++11 ABI 
  [5]   N  2015-02-02  New portage plug-in sync system
  [6]   N  2015-07-25  Python 3.4 enabled by default
  [7]   N  2015-08-13  OpenSSH 7.0 disables ssh-dss keys by default
  [8]   N  2015-10-22  GCC 5 Defaults to the New C++11 ABI
  [9]   N  2016-06-19  L10N USE_EXPAND variable replacing LINGUAS
  [10]  N  2018-01-30  Portage rsync tree verification
  [11]  N  2018-03-13  Portage rsync tree verification unstable

-- 
Walter Dnes <waltdnes@waltdnes.org>

[-- Attachment #2: outputs.txt.gz --]
[-- Type: application/octet-stream, Size: 1969 bytes --]