From nobody Sun Oct 22 04:12:28 2023 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SClKV2JKJz4y1hg for ; Sun, 22 Oct 2023 04:12:46 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb2e.google.com (mail-yb1-xb2e.google.com [IPv6:2607:f8b0:4864:20::b2e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SClKT4xJ7z4Ql7 for ; Sun, 22 Oct 2023 04:12:45 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb2e.google.com with SMTP id 3f1490d57ef6-d9ac31cb051so2158930276.3 for ; Sat, 21 Oct 2023 21:12:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697947964; x=1698552764; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Sx1E7UTrwq+p36QwdLZNIVpirUNQUN7PRF69irsx1fo=; b=a4ZQnhF+oCMH8Iboa34Brz1Fq50K3RTCrzJpvXL7VFR6FY02/UVGXfSkNcDeYJo/Am VvIAdL5fpazVN8X43vq+l4sYxMti2hPVkdHpeTfB1KevtU7DZqyDqkDDlXBonkjpJx4B 16k1+HzAhonDrcCrHnWKDs1ftWvLXcQAgq6EQVs++3NZr86YwBmoxxbbxuCmcLUe4sZC F406xxpzqUpz94JqVhhu11LxiL1T7QXDxJqKr6sxt+NeAnvjEwHMcDImGklvc4UYUn2D /TTiLHAGwlN+5RnEnA6PT5MSoDgGe+KKmjpfDsKGKVuDfS2wg6c8vGlAE0kJQgT573Mg giFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697947964; x=1698552764; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Sx1E7UTrwq+p36QwdLZNIVpirUNQUN7PRF69irsx1fo=; b=hjqyxQvbA5YgqSCPS+t5ea9x2df5biqCUo4CcsPshzfhILpRSjw3/Q6NAkGPAhVZrb JJAlsf7xnugR5/bthNoLwpv5ajQxj3A8AMSsddnio9EfHZJHogueTsSa2NHkZWyTdj3Q GvDBuAldoZe9/QdKc5qrIb1XOKG3PkRIGw4qwcr0fujWx4Scw0OteLg2X+LcPT4Z9W4i ej1b8Lt4q8K2uQzBSidaya0dJPcXslqjWSF0xTyzXKzV/3t45ka1NkYjoizBnDLPYgQf 363wLviIAi0nis9ckgRJuWTcZ5qdex0BjNyLKy8Ccx0DWJTKga8/CetmdI6Bpjy7gkLy AMJg== X-Gm-Message-State: AOJu0Yw7iXp1jDbHa88Pd4nhQJlrPKxjK35vx8+2odo0liSQM1ohQ/F3 LCEEg4jAzyQ4DAPqfC62g3ZpGYeHEG+lM27qjSZHOXaASIk= X-Google-Smtp-Source: AGHT+IFKgWkXZPabEIsREM3ORlPXFlUnnfmfi/0QKu7j8n4Mm0ZGAujGuOi4OicHhpgC07XkRcosjnbbcstzpNGn6hM= X-Received: by 2002:a25:68cb:0:b0:d9a:6855:14cd with SMTP id d194-20020a2568cb000000b00d9a685514cdmr6067704ybc.39.1697947964656; Sat, 21 Oct 2023 21:12:44 -0700 (PDT) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: <202310211305.39LD5Qt8086896@nuc.oldach.net> In-Reply-To: From: Kevin Oberman Date: Sat, 21 Oct 2023 21:12:28 -0700 Message-ID: Subject: Re: lang/perl5.36: update procedure written in UPDATING is not enough To: Tatsuki Makino Cc: "freebsd-ports@FreeBSD.org" Content-Type: multipart/alternative; boundary="00000000000047d22c06084651e8" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4SClKT4xJ7z4Ql7 --00000000000047d22c06084651e8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Oct 21, 2023 at 5:10=E2=80=AFPM Tatsuki Makino wrote: > Helge Oldach wrote on 2023/10/21 14:49: > > portupgrade -f `pkg query %ro-%rv lang/perl5.28` > > In the case of portmaster, it is portmaster -r perl5- . > Reinstalling everything listed in `pkg info -q -r perl5` like this is > overkill. > Perhaps that is why the method that used to be "portmaster -r perl5-" > (20141126) is now using "portmaster -f `pkg shlib -qR libperl.so.5.26`". > > Most of *.pm files installed in /usr/local/lib/perl5/site_perl/mach/5.36/ > use DynaLoader, so most ports that install it have a library linked to > libperl.so.5.36. > So, those ports are targeted for updating as per the procedure. > > Ports that are not targeted for updating in this procedure, but need to b= e > reinstalled, seem to create a file named .packlist in > /usr/local/lib/perl5/site_perl/mach/5.36/ directory. > Port like p5-Text-CSV-2.03 (textproc/p5-Text-CSV) is such ports. > > Reinstalling all p5-* ports is slight but overkill. > Port like p5-SGMLSpm-1.03_2 (textproc/p5-SGMLSpm) is such ports. > It doesn't seem to have a file that involves the old version number. > The only reason it doesn't have a .packlist could be because it hasn't > been reinstalled in a long time :) > > Since perl scripts are byte-compiled and then executed, there should be n= o > problem if a file in a running script is replaced. > The new file will be used from the next run. > > Regards. > I think portmaster has a bug. As per the man page, the behavior of '-f' matches the behavior of '-R -f". Actually, I'm unclear on what the purpose '-f' is. If you run portmaster with no options on a port that is up to date, it still reinstalls it and has for a very long time, maybe always. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --00000000000047d22c06084651e8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Oct 21, 2023 at 5:10=E2= =80=AFPM Tatsuki Makino <t= atsuki_makino@hotmail.com> wrote:
Helge Oldach wrote on= 2023/10/21 14:49:
> portupgrade -f `pkg query %ro-%rv lang/perl5.28`

In the case of portmaster, it is portmaster -r perl5- .
Reinstalling everything listed in `pkg info -q -r perl5` like this is overk= ill.
Perhaps that is why the method that used to be "portmaster -r perl5-&q= uot; (20141126) is now using "portmaster -f `pkg shlib -qR libperl.so.= 5.26`".

Most of *.pm files installed in /usr/local/lib/perl5/site_perl/mach/5.36/ u= se DynaLoader, so most ports that install it have a library linked to libpe= rl.so.5.36.
So, those ports are targeted for updating as per the procedure.

Ports that are not targeted for updating in this procedure, but need to be = reinstalled, seem to create a file named .packlist in /usr/local/lib/perl5/= site_perl/mach/5.36/ directory.
Port like p5-Text-CSV-2.03 (textproc/p5-Text-CSV) is such ports.

Reinstalling all p5-* ports is slight but overkill.
Port like p5-SGMLSpm-1.03_2 (textproc/p5-SGMLSpm) is such ports.
It doesn't seem to have a file that involves the old version number. The only reason it doesn't have a .packlist could be because it hasn= 9;t been reinstalled in a long time :)

Since perl scripts are byte-compiled and then executed, there should be no = problem if a file in a running script is replaced.
The new file will be used from the next run.

Regards.

I think portmaster has a = bug. As per the man page, the behavior of '-f' matches the behavior= of '-R -f".=C2=A0 Actually, I'm unclear on what the purpose &= #39;-f' is. If you run portmaster with no options on a port that is up = to date, it still reinstalls it and has for a very long time, maybe always.=


--
Kevin Ob= erman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--00000000000047d22c06084651e8--