a while ago I briefly discussed merging our settings packages into one source, which currently looks like this:
kubuntu-settings/ kubuntu-settings/active kubuntu-settings/desktop kubuntu-settings/low-fat kubuntu-settings/netbook now the question is how to structure the binary.... yofel argued that perhaps we should have only one kubuntu-settings binary, this however is somewhat unfavorable IMHO as you then get unrelated plunder everywhere, plus if the need to add artwork to any of those arises it would be introduced on all platforms even if not needed. for me the best layout would be: * kubuntu-settings-base * kubuntu-settings-desktop - depends on settings-base - contains desktop and netbook overlays ontop of base * kubuntu-settings-active & kubuntu-settings-low-fat - depend on settings-base base then holds all the common stuff (font settings for example) and all other settings cascade on top of it. this in particular allows for a very tiny base package and faster cascading for active (fewer existing files to check for settings = faster) another option would be to continue using desktop as base and have everything cascade ontop of that opinions? also, kubuntu-settings-foo or kubuntu-foo-settings (I personally find former more accessible from an auto-complete perspective) HS
-- kubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
