Next | Query returned 25 messages, browsing 1 to 10 | Previous

History of commit frequency

CVS Commit History:


   2023-08-14 07:25:36 by Thomas Klausner | Files touched by this commit (1247)
Log message:
*: recursive bump for Python 3.11 as new default
   2023-06-06 14:42:56 by Taylor R Campbell | Files touched by this commit (1319)
Log message:
Mass-change BUILD_DEPENDS to TOOL_DEPENDS outside mk/.

Almost all uses, if not all of them, are wrong, according to the
semantics of BUILD_DEPENDS (packages built for target available for
use _by_ tools at build-time) and TOOL_DEPEPNDS (packages built for
host available for use _as_ tools at build-time).

No change to BUILD_DEPENDS as used correctly inside buildlink3.

As proposed on tech-pkg:
https://mail-index.netbsd.org/tech-pkg/2023/06/03/msg027632.html
   2022-08-31 10:07:19 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
ninja-build: updated to 1.11.1

v1.11.1
This is a hotfix release for a SIGFPE on Linux
   2022-05-27 14:22:35 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
ninja-build: updated to 1.11.0

release 1.11

This release adds Validation Nodes which are a new way to add jobs like linters \ 
or static analyzers to the build graph. They are added using |@ and don't \ 
produce any outputs. You can read more about the motivation and the syntax here: \ 
https://github.com/ninja-build/ninja/pull/1800

Another big change is that Ninja now uses UTF-8 on Windows. This means that \ 
while previous versions of Ninja used the local ANSI encoding it will now always \ 
use UTF-8 allowing filenames and output with special characters. For this to \ 
work you'll need Windows 10 Version 1903 or newer. And for the console output to \ 
show Unicode characters you'll need to set the codepage to 65001. More \ 
information at: https://github.com/ninja-build/ninja/pull/1915

Note that this is a breaking change if you relied on non-ASCII characters of the \ 
local codepage! If you want to query Ninja what codepage it uses in your \ 
generator, call `ninja -t wincodepage` and act accordingly.

There are also two new tools:
missingdeps: https://github.com/ninja-build/ninja/pull/1331
inputs: https://github.com/ninja-build/ninja/pull/1730

And as it was often requested, ninja now has a --quiet flag :)

For a complete list of changes see \ 
https://github.com/ninja-build/ninja/milestone/3?closed=1
   2021-10-26 12:20:11 by Nia Alarie | Files touched by this commit (3016)
Log message:
archivers: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Could not be committed due to merge conflict:
devel/py-traitlets/distinfo

The following distfiles were unfetchable (note: some may be only fetched
conditionally):

./devel/pvs/distinfo pvs-3.2-solaris.tgz
./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip
   2021-10-07 15:44:44 by Nia Alarie | Files touched by this commit (3017)
Log message:
devel: Remove SHA1 hashes for distfiles
   2020-11-29 19:06:56 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
ninja-build: update to 1.10.2.

There have been two small changes in this release: The browse tool
is now enabled when building with CMake (so it's part of the official
binaries again) and it should now work in all circumstances to run
the restat tool by the generator on Windows. See
https://github.com/ninja-build/ninja/issues/1724#issuecomment-677730694
for why the fix in 1.10.1 wasn't enough.
   2020-08-19 10:52:44 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
ninja-build: updated to 1.10.1

v1.10.1
See https://groups.google.com/g/ninja-build/c/QQM54eAhrjU/m/q5zn_zTlAQAJ for the \ 
v1.10.1 release notes.
   2020-07-06 12:48:34 by Jonathan Perkin | Files touched by this commit (1)
Log message:
ninja-build: Support mksh-enabled macOS installs.
   2020-04-21 09:48:55 by David Sainty | Files touched by this commit (3)
Log message:
Support a shell other than /bin/sh as a workaround for MacOS X.

Under MacOS X the LD_LIBRARY_PATH variable is unset by the build system
running executables under /bin (namely /bin/sh).  This is part of MacOS X
System Integrity Protection.

Because many (most?) users of ninja/meson seem to need hacks involving
LD_LIBRARY_PATH, use a non-SIP-triggering shell under MacOS X.

Fixes MacOS X builds of glib2, gobject-introspection and others.

Bump PKGREVISION for the new behaviour under MacOS X.

Next | Query returned 25 messages, browsing 1 to 10 | Previous