I was thing about something like 3 base functionalities (with respect to configured repositories):
feature:install - installs a feature, all sub-featirues, bundles, ... (I guess nothing needs to change here) feature:remove - removes the feature only. All sub-features, bundles, are not touched! Perhaps there could be "-r" option to remove sub-features as well but bundles will always remain unchanged feature:list - shows bundles installed by a feature * even if the feature is not installed * bundle:provided-by - shows features that install that bundle (even if those are not currently installed) Given those above one could then script / develop all kind of helper command / tools. Like for example : autoclean - removes all bundles that were (1) installed as part of a feature which was removed and (2) no other feature point to them forced-remove - removes all bundles that were installed by given feature even if in use .... Does it make sense? On Tue, Apr 14, 2015 at 9:11 AM, Christian Schneider < [email protected]> wrote: > Very well possible. What is the algorithm in Linux? > > Christian > > On 14.04.2015 09:06, Milen Dyankov wrote: > >> Please correct me if I'm wrong but aren't we talking about a problem that >> (at least conceptually) has been solved? Package management has been >> around >> in Linux for quite some time. Can't features just mimic the same behavior? >> From my perspective features are quite similar to virtual packages in >> Debian based linux distributions. >> >> Best, >> Milen >> 14 kwi 2015 08:54 "Christian Schneider" <[email protected]> >> napisał(a): >> >> > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com > > -- http://about.me/milen
