Re: Splitting pkgmgr and portmgr
- In reply to: Baptiste Daroussin : "Splitting pkgmgr and portmgr"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 07 Oct 2022 11:43:29 UTC
October 7, 2022 at 1:38 PM, "Tomoaki AOKI" <junchoon@dec.sakura.ne.jp> wrote: > > On Fri, 7 Oct 2022 12:49:23 +0200 > Baptiste Daroussin <bapt@FreeBSD.org> wrote: > > > > > Hello everyone, > > > > It's been a while since the ports management team (portmgr) needed some > > modernization and updates. To meet today's requirements, we are taking a first > > step: spliting portmgr and pkgmgr. > > > > While portmgr's charter does not change, the part of the responsibility > > regarding the packages management will now be delegated to pkgmgr under the > > portmgr umbrella. > > > > Package management (pkgmgr) team: > > - its role is to work on the technical side of the package production: > > + building official packages. > > + running exp-runs. > > + maintaining and upgrading the package build infrastructure. > > - This team will be composed of people that are not part of the portmgr team > > (no votes for instance) but still will receive the portmgr emails (like > > lurkers) in a advisory function. Working on the package build > > > > It would be worth considering to contain INDEX build. > Not all, but some of the causes of broken INDEX also causes package > builds. > > For these cases, giving the authority of forcibly fix/revert > offending commit(s) to pkgmgr should greatly help, especially for > commits just before weekly package build starts. We cannot list everything, but yes it is considered part of it. Best regards, Bapt