[20:17:02] <few_> zmedico: what happend to sets support? [20:17:09] <few_> or better hwat did not happen ;) [20:17:22] <few_> can't we just release what's there [20:17:38] <few_> file based sets are the most useful stuff anyway [20:17:46] <few_> and those are usable [20:18:00] <zmedico> well, I guess that part that works is fine to release, though I'd keep the apis private [20:18:49] <zmedico> not really interested in supporting those apis atm [20:19:50] <few_> well, I don't care about the apis. maybe dol-sen would like to see parts of it available [20:19:56] <few_> anyway do it! [...] [20:25:39] <zmedico> so, basically just a way to split up world into subsets [20:26:02] <zmedico> using world_sets and /etc/portage/sets [20:27:35] <few_> yeah
I think all we have to do is tweak SetConfig._create_default_config() and add some docs to man/portage.5
We should also tweak ensure_required_sets() and setconfig_fallback() to match the new SetConfig._create_default_config() configuration.
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=c5142aadedee5b1917607f10d5018b763ef2419b
Documentation updates: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=5f252c72350e1671ad01630e90d5acb2226629e3
This is fixed in 2.1.11 and 2.2.0_alpha111.
This feature attempts to get further near a portage-2.2 release. This could have been indicated with a version bump to portage-2.1.85 (instead of portage-2.1.11)