Meta pkgs

filmor edited this page Nov 15, 2012 · 2 revisions
Clone this wiki locally

I think it is easier to manage things, if we separate ebuilds for installer, client and games and make the latter two meta ebuilds that pull in dependencies and print some user info.

steam-meta will depend on steam-client-meta and conditionally on game engines that in turn can depend on game-specific packages.

Pros:

  • Games or game engines could get their own meta ebuild and could become dependencies adding use-flags to steam-meta.
  • steam-installer can be unmerged after installation without interference with client dependencies

Cons:

  • Several meta ebuilds only for dependencies
  • When uninstalling the installer this also removes the global launcher (/usr/bin/steam) which is needed for the URLs to work, so keeping it installed does make sense