Consider merging ebuilds from steam overlay to Galapagos tree

[Elizafox]

Steam is definitely a "nice to have" although non-free. I'll be the maintainer for these ebuilds if we decide to merge.

[mjeveritt]

Propose we start an 'official' maintained Steam overlay, if you're happy to maintain? We can put 'official' into the repo description if desired, but think to maintain licensing separation, would be better to keep separate from main tree. Although, depending on what 'ulm@g' might suggest regarding licensing of main tree items, we could add Steam license to the Portage licenses .. I dunno.

[Elizafox]

We already have EULA builds in the tree and steam is a commonly requested item, especially since Valve has cranked up the heat on developers (Steam OS and all). There is a steam overlay from gentoo that functions, but I would like something more official.

[shentino]

Why don't we handle this the way Gentoo does?

We can always use the license system to let end users weed out classes of software they don't want.

If it's popular enough for our userbase that itself is a good reason to include it IMHO. Once demand is established all we need to do IIRC is keep the metadata straight.

General opinion:

• If it's popular and there isn't a major ideological reason to oppose it on principle (like for example sys-malware/govrootkit-6.6.6) it should go in the tree and get some support
• If there's philosophical issues, use metadata to flag it accordingly for portage so that users with concerns can configure their masking appropriately.