Re: [gentoo-news] 2026-03-29-varnish-renamed-vinyl-cache: add news item

Brett A C Sheffield <[email protected]> writes:

> Signed-off-by: Brett A C Sheffield <[email protected]>

Remember to CC pr@, per
https://devmanual.gentoo.org/general-concepts/news/index.html.

> ---
>  ...6-03-29-varnish-renamed-vinyl-cache.en.txt | 50 +++++++++++++++++++
>  1 file changed, 50 insertions(+)
>  create mode 100644 2026-03-29-varnish-renamed-vinyl-cache/2026-03-29-varnish-renamed-vinyl-cache.en.txt
>
> diff --git a/2026-03-29-varnish-renamed-vinyl-cache/2026-03-29-varnish-renamed-vinyl-cache.en.txt b/2026-03-29-varnish-renamed-vinyl-cache/2026-03-29-varnish-renamed-vinyl-cache.en.txt
> new file mode 100644
> index 0000000..d852159
> --- /dev/null
> +++ b/2026-03-29-varnish-renamed-vinyl-cache/2026-03-29-varnish-renamed-vinyl-cache.en.txt
> @@ -0,0 +1,50 @@
> +Title: www-servers/vinyl-cache-9.0.0: Varnish Renamed to Vinyl-Cache

We don't put versions in the title like that, but this also exceeds 20
characters (see devmanual and https://www.gentoo.org/glep/glep-0042.html#id27).

> +Author: Brett A C Sheffield <[email protected]>
> +Posted: 2026-03-29
> +Revision: 1
> +News-Item-Format: 2.0
> +Display-If-Installed: <www-servers/varnish-9.0.0
> +

D-I-F is always a bit thorny, and perhaps should be explained more in
the devmanual.

The problem is, by using <, you hide the news item from anyone who
upgrades first and checks news later. Should users do that? Ideally
not, but some will, and then this will catch them out.

The downside is that you end up showing it to stable users who aren't
yet being upgraded.

> +As of version 9.0.0, www-servers/varnish has been renamed to
> +www-servers/vinyl-cache in line with upstream's change of name. The name change

I'd do "[0]" here and add it to the link at the end of the news item.

> +also affects binaries, directories, init scripts, configuration and the user and
> +group used by server daemon.
> +
> +If you are upgrading from a previous version of www-servers/varnish you will
> +need to update your configuration as described below.

I try to add headings to help people sa they often skim or get
overwhelmed by a lot of text.

> +
> +All references to varnishd, varnishlog, varnishncsa and varnishadm are replaced
> +with their vinyl* equivalents:
> +
> + varnishd    -> vinyld
> + varnishlog  -> vinyllog
> + varnishncsa -> vinylncsa
> + varnishadm  -> vinyladm
> +
> +The following files have been renamed:
> +
> + /etc/conf.d/varnishd    -> /etc/conf.d/vinyld
> + /etc/conf.d/varnishlog  -> /etc/conf.d/vinyllog
> + /etc/conf.d/varnishncsa -> /etc/conf.d/vinylncsa
> + /etc/init.d/varnishd    -> /etc/init.d/vinyld
> + /etc/init.d/varnishlog  -> /etc/init.d/vinyllog
> + /etc/init.d/varnishncsa -> /etc/init.d/vinylncsa
> +

Have systemd units been renamed?

> +In the above files, all VARNISH* options are now VINYL* and you will need to
> +update your configuration accordingly.
> +
> +The configuration directory has been moved:
> + /etc/varnish/ -> /etc/vinyl-cache/
> +
> +To upgrade from varnish 8.x to 9.x:
> +
> +0) Take a backup of your existing configuration files
> +1) Stop all running varnish services
> +2) emerge --oneshot www-servers/vinyl-cache
> +3) Update and install your VCL files in /etc/vinyl-cache/
> +
> +You can now start the new vinlyld, vinyllog and vinylncsa services,
> remembering

typo: vinyld

> +to add them to the appropriate runlevels as normal.
> +
> +For more details of the changes, you are encouraged to read:
> +https://vinyl-cache.org/docs/9.0/whats-new/upgrading-9.0.html

-----BEGIN PGP SIGNATURE-----

iQEBBAEWCgCpFiEEJaa7iN2bdkxrVUHCc4QJ9SDfkZAFAmnJWUMbFIAAAAAABAAO
bWFudTIsMi41KzEuMTIsMiwyXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25z
Lm9wZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQyNUE2QkI4OEREOUI3NjRDNkI1NTQx
QzI3Mzg0MDlGNTIwREY5MTkwDxxzYW1AZ2VudG9vLm9yZwAKCRBzhAn1IN+RkAb7
AP91Y56f7bgbTZYljeXt5qV72WN+QQKG4vx6yA2rFOOu1AD/YJ4BOLryseHLusL9
xjRpXJwQsJYzxiFZIyMmAkEAngU=
=FiVw
-----END PGP SIGNATURE-----