tech-pkg archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Preparing for pkgsrc-2026Q1 - entering careful period 2
Hi all,
In the hopes of having a successful 2026Q1, we now have restrictions on
riskier package changes. Please request approval for the following types
of changes:
- rust
- firefox
- gtk3
- wayland
- cmake
- non-micro updates to pbulk, distcc, ccache, and similar things that
have non-trivial use to build packages at scale
- non-micro updates to widely-used non-versioned languages (e.g. perl
5.X->5.X+1, ocaml)
- changing the default version of versioned languages and systems (e.g.
go, guile, php, python, ruby, postgresql, mysql)
- non-micro updates to packages with more than 500 (recursive)
dependencies
The restrictions from the previous period still apply:
- any package always needing approval (boost, gmake, qt5) - the
standard answer will be wait until after the branch
- any change in mk that is intended to result in build failures
(typically for things that were warnings before)
- clang/llvm (New versions almost always are backwards incompatible.)
- poppler* (frequent API changes)
- Any package with a history of a troubled update in the last 3 years:
- glib2
- py-sip6
The list of restrictions is documented in https://pkgsrc.org/quarterly/
(and can be discussed if you want to make changes to it).
This is not a pkgsrc freeze, that will start on the weekend of March
14/15.
Thanks for working on pkgsrc,
Maya
Home |
Main Index |
Thread Index |
Old Index