• Re: updating a single port: www/chromium

    From Bugs Beastie@bugsbeastie@gmail.com to muc.lists.freebsd.ports on Fri Oct 30 16:31:42 2026
    From Newsgroup: muc.lists.freebsd.ports

    Oct 30, 2026 15:53:23 Matthias Apitz <guru@unixarea.de>:

    Hello,

    Hi!

    [snip]
    What would be the best/correct way to update such a port and not risking
    that poudriere re-builds a big amount of the 2300 ports?

    I think cherry-picking commit that fixes your problem and closest to your ports tree from the git history is the best option. Sometimes you need only one specific patch. You put the updated/patched port in the poudriere overlay.

    My 0.02c,
    Alexey


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From void@void@f-m.fm to muc.lists.freebsd.ports on Sat Oct 31 05:38:39 2026
    From Newsgroup: muc.lists.freebsd.ports

    --qNRJk+kRJ0O2hkZY
    Content-Type: text/plain; charset=us-ascii; format=flowed
    Content-Disposition: inline
    Content-Transfer-Encoding: quoted-printable

    Hi,
    On Fri, Oct 30, 2026 at 03:52:51PM +0100, Matthias Apitz wrote:

    What would be the best/correct way to update such a port and not risking
    that poudriere re-builds a big amount of the 2300 ports?

    I'd just run a build (after updating the ports tree) with

    'poudriere bulk -j buildername -J-numberofcores www/chromium'
    that way chromium plus any updated dependencies it needs gets
    rebuilt. I'd expect a number of ports to get rebuilt but
    would be surprised if it's even a quarter of your total number.

    note: ports-mgmt/poudriere-dsh2dsh is better at skipping needless
    rebuilds than standard poudriere the last time I looked. This is what
    I use.
    --=20
    void<at>f-m.fm | GPG fingerprint: BD97 5B52 1B78 B7A9 AFFE 7DD4 FD32 D1F9 = 0814 DECD
    Please don't Cc: as I'm already subscribed to the list.

    --qNRJk+kRJ0O2hkZY
    Content-Type: application/pgp-signature; name=signature.asc

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

    iJEEABYKADkWIQS9l1tSG3i3qa/+fdT9MtH5CBTezQUCauV+yBsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwyLDMACgkQ/TLR+QgU3s1OOwD+PdIMvcdCieACidvTFt+l QqNOGg2JoE7LRdtER3ZDac0BAL/ZGfVhzLc6e+8+IUMhyQGJEczCnoh/9/AzWIow
    wkML
    =fUne
    -----END PGP SIGNATURE-----

    --qNRJk+kRJ0O2hkZY--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.ports on Sat Oct 31 08:40:28 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 10/30/26 22:38, void wrote:
    Hi,
    On Fri, Oct 30, 2026 at 03:52:51PM +0100, Matthias Apitz wrote:

    What would be the best/correct way to update such a port and not risking
    that poudriere re-builds a big amount of the 2300 ports?

    I'd just run a build (after updating the ports tree) with

    'poudriere bulk -j buildername -J-numberofcores www/chromium'
    that way chromium plus any updated dependencies it needs gets
    rebuilt. I'd expect a number of ports to get rebuilt but
    would be surprised if it's even a quarter of your total number.

    note: ports-mgmt/poudriere-dsh2dsh is better at skipping needless
    rebuilds than standard poudriere the last time I looked. This is what
    I use.

    For poudriere-devel there is also PKG_NO_VERSION_FOR_DEPS=yes for use in poudriere.conf types of files. With that, poudriere only rebuilds what
    pkg would upgrade. Historically poudriere-devel also did various
    rebuilds that pkg would not later upgrade to, such as: if the major
    version for a .so dependency had not actually changed.

    In essence, various builds actually end up being a quick inspection
    activity instead that leads to avoiding the actual build. So the actual
    build count ends up being smaller (when not counting the inspections).

    If the inspection finds a .so major version change is involved in the dependencies, that was not otherwise noticed, it leads to the build
    being done as pkg would do the upgrade.

    This does mean that bulk -n results do not report the improvement, as
    later inspections are dependent on prior rebuilds that do happen to
    occur in the bulk build so the actual build count is not known up front.

    PKG_NO_VERSION_FOR_DEPS is not listed in poudriere.conf.sample yet and
    "man -K PKG_NO_VERSION_FOR_DEPS" output is empty still.
    --
    ===
    Mark Millard
    marklmi at yahoo.com


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ronald Klop@ronald-lists@klop.ws to muc.lists.freebsd.ports on Sat Oct 31 17:12:01 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_3645_903878598.1793463121621
    Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit

    Does https://www.freshports.org/ports-mgmt/portdowngrade/ work with git?

    Regards,
    Ronald.


    Van: Bugs Beastie <bugsbeastie@gmail.com>
    Datum: vrijdag, 30 oktober 2026 16:31
    Aan: Matthias Apitz <guru@unixarea.de>
    CC: freebsd-ports@freebsd.org
    Onderwerp: Re: updating a single port: www/chromium

    Oct 30, 2026 15:53:23 Matthias Apitz <guru@unixarea.de>:

    Hello,

    Hi!

    [snip]
    What would be the best/correct way to update such a port and not risking that poudriere re-builds a big amount of the 2300 ports?

    I think cherry-picking commit that fixes your problem and closest to your ports tree from the git history is the best option. Sometimes you need only one specific patch. You put the updated/patched port in the poudriere overlay.

    My 0.02c,
    Alexey






    ------=_Part_3645_903878598.1793463121621
    Content-Type: text/html; charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    Does <a href=3D"https://www.freshports.org/ports-mgmt/portdowngrade/">https= ://www.freshports.org/ports-mgmt/portdowngrade/</a> work with git?<br />
    <br />
    Regards,<br />
    Ronald.<br />
    <br />
    =C2=A0
    <p><strong>Van:</strong> Bugs Beastie &lt;bugsbeastie@gmail.com&gt;<br /> <strong>Datum:</strong> vrijdag, 30 oktober 2026 16:31<br /> <strong>Aan:</strong> Matthias Apitz &lt;guru@unixarea.de&gt;<br /> <strong>CC:</strong> freebsd-ports@freebsd.org<br /> <strong>Onderwerp:</strong> Re: updating a single port: www/chromium</p>

    <blockquote style=3D"padding-right: 0px; padding-left: 5px; margin-left: 5p=
    x; border-left: #000000 2px solid; margin-right: 0px">
    <div class=3D"MessageRFC822Viewer" id=3D"P">
    <div class=3D"TextPlainViewer" id=3D"P.P">Oct 30, 2026 15:53:23 Matthias Ap= itz &lt;guru@unixarea.de&gt;:<br />
    <br />
    &gt; Hello,<br />
    &gt;<br />
    Hi!<br />
    <br />
    &gt; [snip]<br />
    &gt; What would be the best/correct way to update such a port and not riski= ng<br />
    &gt; that poudriere re-builds a big amount of the 2300 ports?<br />
    &gt;<br />
    I think cherry-picking commit that fixes your problem and closest to your p= orts tree from the git history is the best option. Sometimes you need only = one specific patch. You put the updated/patched port in the poudriere overl= ay.<br />
    <br />
    My 0.02c,<br />
    Alexey<br />
    =C2=A0</div>

    <hr /></div>
    </blockquote>
    <br />
    =C2=A0
    ------=_Part_3645_903878598.1793463121621--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mark Millard@marklmi@yahoo.com to muc.lists.freebsd.ports on Sat Oct 31 12:12:39 2026
    From Newsgroup: muc.lists.freebsd.ports

    On 10/31/26 08:40, Mark Millard wrote:
    On 10/30/26 22:38, void wrote:
    Hi,
    On Fri, Oct 30, 2026 at 03:52:51PM +0100, Matthias Apitz wrote:

    What would be the best/correct way to update such a port and not risking >>> that poudriere re-builds a big amount of the 2300 ports?

    I'd just run a build (after updating the ports tree) with

    'poudriere bulk -j buildername -J-numberofcores www/chromium'
    that way chromium plus any updated dependencies it needs gets
    rebuilt. I'd expect a number of ports to get rebuilt but
    would be surprised if it's even a quarter of your total number.

    note: ports-mgmt/poudriere-dsh2dsh is better at skipping needless
    rebuilds than standard poudriere the last time I looked. This is what
    I use.

    For poudriere-devel there is also PKG_NO_VERSION_FOR_DEPS=yes for use in poudriere.conf types of files. With that, poudriere only rebuilds what
    pkg would upgrade. Historically poudriere-devel also did various
    rebuilds that pkg would not later upgrade to, such as: if the major
    version for a .so dependency had not actually changed.

    In essence, various builds actually end up being a quick inspection
    activity instead that leads to avoiding the actual build. So the actual
    build count ends up being smaller (when not counting the inspections).

    If the inspection finds a .so major version change is involved in the dependencies, that was not otherwise noticed, it leads to the build
    being done as pkg would do the upgrade.

    This does mean that bulk -n results do not report the improvement, as
    later inspections are dependent on prior rebuilds that do happen to
    occur in the bulk build so the actual build count is not known up front.

    PKG_NO_VERSION_FOR_DEPS is not listed in poudriere.conf.sample yet and
    "man -K PKG_NO_VERSION_FOR_DEPS" output is empty still.


    Turns out there is some public documentation:

    <https://github.com/freebsd/poudriere/blob/master/docs/pkg_no_version_for_deps.md>

    and there is some related background information:

    <https://github.com/freebsd/poudriere/blob/master/docs/shlib_tracking.md>
    --
    ===
    Mark Millard
    marklmi at yahoo.com


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.22a-Linux NewsLink 1.2