Packages with versions in their names (e.g. py37- or -emacs26-)

[Joseph Mingrone]

The major version of editors/emacs will soon be updated from 26 to 27.
This means, with the way our flavored packages are now named, packages
like pdf-tools-emacs26-0.90.41 will change to pdf-tools-emacs27-0.90.41.

If users just do `pkg upgrade`, even with a PORTREVISION bump,
pdf-tools-emacs26-0.90.41, e.g., will not be upgraded.  Users must first
do something like

   pkg set -yn "pdf-tools-emacs26-0.90.41":"pdf-tools-emacs27-0.90.41"

I can think of a few ways we could make it, so that users do not have to
complete this extra `pkg set -yn...` step.

1. Change the way the packages are named, so that the Emacs major
version is not included in the package name.  We could change the
packages name like this:

- pdf-tools-emacs27-0.90.41 -> pdf-tools-emacs-0.90.41
- pdf-tools-emacs28-0.90.41 -> pdf-tools-emacs-devel-0.90.41
- tablist-emacs28_nox-1.0_2 -> tablist-emacs-devel_nox-1.0_2
- auctex-emacs26_canna-12.2 -> auctex-emacs_canna-12.2

The downside to this solution is that it's more churn and some package
names would become longer.

2. Hack up pkg, so that it somehow recognizes, that for the same port
origin, only emacs26 changed to emacs27 in the package name, so do the
upgrade.  I am not familiar with pkg's internals, so there may be
constraints that I'm not aware of.

3. Automatically run the `pkg set -yn..` command when emacs is upgraded.
This is probably a bad idea.

Maybe it's best to just continue with the way things are?

What do you think?

Joe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 987 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20200811/0886cc22/attachment.sig>