[Octave-bug-tracker] [bug #57522] "pkg unload" does not care for dependencies

[Mike Miller]

Update of bug #57522 (project octave):

                Severity:              3 - Normal => 1 - Wish               
                Priority:              5 - Normal => 3 - Low                
              Item Group:        Incorrect Result => Feature Request        
                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

I think it would be very helpful if the first step here were to clearly decide
and state what the desired behavior will be. If you need to gather input on
the maintainers list, let's do that first.

For example, if the user enters the command "pkg unload A", but package "B" is
loaded and depends on "A", what should happen?

I can imagine quite a few possibilities

* error message, do not unload any packages
* silently unload both A and B
* unload both A and B, warning message about B
* unload A, keep B loaded (current behavior)
* unload A, keep B loaded, warning message that B may not fully work now
* unload A, interactive prompt the user what to do with B
* interactive prompt the user what to do with both A and B

The choice of outcome may depend on whether the user explicitly loaded A or
whether A was only implicitly loaded as a dependency of B, or maybe we want a
consistent outcome regardless of how A became loaded. We currently do not
track the state of whether a package was loaded explicitly or implicitly.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57522>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/