Hi Milen,
up to K3, a feature has just two states: installed or uninstalled.
In K4, we introduced a full lifecycle where in addition of installed and
uninstalled states, a feature can be started or stopped.
Here, we are talking about start/stop commands.
Regards
JB
On 04/14/2015 11:35 AM, Milen Dyankov wrote:
Hi Jean-Baptiste,
perhaps I don't understand what is discussed here and what you meant by "remove
the features lifecycle commands".
Just wanted to share my point of view regarding features. That is, I see
features as deployment option (get needed bundles in place) and not as
bundle lifecycle batch management option. Or to follow up with my linux
example, one will do "apt-get install mysql" which will install also a
bunch of other things apart form mysql itself. But one does not do "apt-get
start/stop mysql" because that does not make sense. So if those are the
commands you think of removing then that's fine with me (although a bundle
start/stop batch job based on feature as grouping option is nice to have in
some cases)
But what is more important for me personally is to be able to tell how a
bundle was installed (stand alone or via feature). AFAIK this is not
something provided in K3
Best,
Milen
On Tue, Apr 14, 2015 at 11:14 AM, Jean-Baptiste Onofré <[email protected]>
wrote:
Hi Milen,
we already have the Jira about what you propose, and it's not K4 related:
it's already for K3.
Regards
JB
On 04/14/2015 11:12 AM, Milen Dyankov wrote:
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
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
