Comment # 12 on bug 1175119 from Nicolas Nattermann

(patrick.schaaf@yalwa.com here, CTO, I set up this stuff years ago....)

Yalwa_Client is indeed the product name used in our own internal repository,
which we add on for all our client installs. Actual setup for creating it has
been cobbled together back in suse 11.4 days or something like that, and worked
fine moving forward with just version number (and neccessary content) changes.

Here is the "contents" file as it looks right now - hope that is the
information you are looking for:

VENDOR Yalwa GmbH
PRODUCT Yalwa_Client
LABEL Yalwa Client
VERSION "15.0"
RELEASE "338"
ARCH.x86_64 x86_64 i686 i586 i486 i386 noarch
ARCH.i686 i686 i586 i486 i386 noarch
ARCH.i586 i586 i486 i386 noarch
BASEARCHS i586 x86_64
DESCRDIR setup/descr
DATADIR rpm
META SHA1 c6138d37528e0ee2fc4ae0e045fc1de9651876fb  packages
META SHA1 60b4b1ed7f9fd72da8fe43e9e5e71b2185b92479  packages.DU
META SHA1 31aef72fdf731066edf84973be350cd414d6d838  packages.en
KEY SHA1 ab4a01ca4181240c7e0db37d5b86be5662d0b6c3 
gpg-pubkey-a2d24914-4ead7e4b.asc