Login
You're viewing the functional.cafe public feed.
  • Nov 4, 2026, 12:39 PM

    This looks interesting, especially if your hosts are not where your package repo is.

    git-proxy is a caching proxy for package registries. It sits between package managers and their upstream repositories, keeps a local copy of every package it serves, and keeps serving them while the upstream is unreachable.

    My use case: Updating pkg-base jails. After the first install / pkg-update, the packages are local.

    freshports.org/ports-mgmt/git-

    #FreeBSD

    💬 1🔄 2⭐ 0

Replies

  • Nov 5, 2026, 7:23 AM

    @dvl Interesting! Does this keep copies of the packages in the jails' /var/cache/pkg as well?

    Will take a closer look. This should be helpful if you have multiple machines.

    Sofar I've taken the approach of null-mounting /var/db/pkg/repos and /var/cache/pkg into the jail and then running pkg -j <jailname> upgrade from the host.
    Even wrapped pkg in a script so it would mount and unmount, pkg fails if the repo dir is not writable.
    You should be able to find it in codeberg.org/Sp1l/pkg_utils if you're interested.

    Another nag with pkg is that a cache clean command only takes the local pkgs into account, not the ones used in jails...

    💬 1🔄 0⭐ 0
  • Nov 5, 2026, 4:21 PM

    @brnrd To the jail/host, there is no change to how things operate. The only thing[s] you change on the jail is the URL you are fetching from.

    So, yes, /var/cache/pkg acts the same as always.

    Sounds like you need to run pkg-clean in each jail?

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0