Attention Benny Pedersen,

 BP> ebuilds is bash, but portage is 100% python :)

It's usually the python dependent ones that cause all the grief.

 BP> you just create one then

Already have a few bash based ones such as check_install, manifest and a few
others.  They've been in use here for over a decade now but aren't really in
the same league as portage and the such.  Very simple and to the point and lack
 things like dependency tracking and the such.

 BP> glibc 2.28 have problems with crypt, is all i know for now

-={ ':read !ldd /usr/bin/passwd | tr -d "\t"' starts }=-
linux-vdso.so.1 (0x00007fff9db69000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007fd7a0ecf000)
libc.so.6 => /lib/libc.so.6 (0x00007fd7a0d50000)
/lib/ld-linux-x86-64.so.2 (0x00007fd7a0f0a000)
-={ ':read !ldd /usr/bin/passwd | tr -d "\t"' ends }=-

Looks okay from this angle.  passwd is from the shadow-4.6 package which was
compiled with glibc-2.28 which is where the above listed libcrypt.so.1 comes
from.

End transmission.

... Fudd's First Law of Opposition:
    If you push something hard enough, it will fall over.
--- GNU bash, version 4.4.23(1)-release (x86_64-silvermont-linux-gnu)