I won't debate what default behavior might be desirable, but is the behavior 
configurable regarding inactive ports?  If so, there are options some might 
desire between keep all and keep none.  I for instance would always want to 
keep any that still had a dependency on them (it happens, occasionally), and 
would like to be able to keep the most recent one (or other small number) for 
any given port, rather than none or all, to have something to fall back to in 
case of problems, yet limit the growth of space consumed.  Such a limit would 
be particularly useful regarding ports that are either large or frequently 
updated.

> On Apr 7, 2017, at 20:28, Stephen Baber <sbabe...@gmail.com> wrote:
> 
> JPortsUI has been updated due to an error when loading the port index.
> And by request, the program's behavior has been changed from always
> removing inactive ports to ignoring them,  This means previous port
> versions will linger until uninstalled.  The new version can be
> downloaded from
> https://sourceforge.net/projects/jportsui/files/
> 
> Feel free to submit a ticket or feature request with SourceForge's
> "Tickets" navigation button or gmail me.
> 
> Steve
> 

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to