Bug #75816 for App-perlbrew: perlbrew self-update enhancement

Fri Mar 16 10:11:27 2012 rhogaboom [...] industrialdefender.com - Ticket created

Subject:	perlbrew self-update enhancement
Date:	Fri, 16 Mar 2012 10:11:14 -0400
To:	<bug-App-perlbrew [...] rt.cpan.org>
From:	Richard Hogaboom <rhogaboom [...] industrialdefender.com>

When I do a perlbrew self-update it works correctly, however, the output does not give any positive info as to which version I upgraded to. How about doing a 'perlbrew version' both before and after a self-upgrade and printing this along with your standard message? Then the user can tell immediately and exactly which version he came from and which version he upgraded to. perlbrew rocks!! -- Richard A Hogaboom 16 Chestnut Street - Suite 300 Foxborough, MA 02035 rhogaboom@industrialdefender.com richard.hogaboom@gmail.com W508-718-6711 H508-435-4091 C508-330-3775 "Treat your password like your toothbrush, never let anybody else use it and change it every six months." Clifford Stoll

Fri Mar 16 21:42:42 2012 GUGOD [...] cpan.org - Correspondence added

On Fri Mar 16 10:11:27 2012, rhogaboom@industrialdefender.com wrote: Show quoted text

> When I do a perlbrew self-update it works correctly, however, the output > does not give any positive info as to which version I upgraded to. How > about doing a 'perlbrew version' both before and after a self-upgrade > and printing this along with your standard message? Then the user can > tell immediately and exactly which version he came from and which > version he upgraded to. perlbrew rocks!!

you are right, perlbrew needs more attention on its message. I had that in mind in the early releases but sometimes new features does not have document coverage. Thanks for the reminder :)

Fri Mar 16 21:42:43 2012 The RT System itself - Status changed from 'new' to 'open'