Re: www/firefox-esr instead of www/firefox[0-9]*

[Greg Troxel <gdt%lexort.com@localhost>]

"J. Lewis Muir" <jlmuir%imca-cat.org@localhost> writes:

> On 12/17, nia wrote:
>> On Tue, Dec 17, 2019 at 12:46:39PM -0500, Greg Troxel wrote:
>> > I again don't follow why our choice of PKGPATH or PKGNAME has anything
>> > to do with these problems.
>> 
>> 'pkgin upgrade' doesn't work. At all. You get stuck with an insecure,
>> unsupported release until you explicitly do:
>> 
>> `pkgin remove firefox60`
>> `pkgin install firefox68`
>> 
>> Then migrate your profile. 
>
> +1.  IMO, this gets to the heart of the matter and is what's important.
> I want 'pkgin upgrade' to work correctly.  I don't want to have a set
> of packages that are special that I have to keep track of and before
> every upgrade check and see what's the latest version, and then switch
> to that version.  Instead, I just want to be able to say, "I want the
> latest stable version of this package always," and that should mean that
> it receives security updates, it does not become EOL and I'm left still
> running it not knowing that, etc., and 'pkgin upgrade' should do the
> right thing and keep me in a good and secure state.

That's a fair point.  But we already have that for firefox, and it's
called "firefox".   The issue here is people that want to run an older
version on purpose, with a more complicated notion of when to uprade.