[TimQuelch]

• Update cmake config to account for upstream changes in versioning and
  extension build behaviour in 2.0
• Move extension and excluded test pattern config to top level attribute
  to allow easier overriding in overlays. For example this makes adding
  additional extensions to build and link easier
• Add additional unit test that requires network stack to exclusions for
  install check

Things done

• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.
• Follows the automation/AI policy.
• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • aarch64-darwin
• Tested, as applicable:
  • Basic functionality of all binary files, usually in ./result/bin/.
  • Ran nixpkgs-review on this PR. See nixpkgs-review usage.
  • Package tests at passthru.tests.
  • NixOS tests in nixos/tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.

[81reap]

the obdc driver was updated to 2.0 and it is doesn't fully work until this PR can merge :: #576954

this also superceeds :: #568519

edit :: I have opened a PR to help matain the duckdb packages :: #579506

[cameronraysmith]

#576954 is merged.

#579992 proposes to fix the excessive logging output issue prior to duckdb 2.0. However, if @jonasgloning agrees, we could consider reviewing this PR instead.

@TimQuelch , if you look back through the history of recent duckdb PRs that have been merged like #545407 , you'll note we have started targeting PRs that modify the duckdb derivation like this one at the staging branch rather than master due to the large number of derivations in the duckdb closure #579495 (review). Could you rebase upon and retarget to staging instead of master?

[TimQuelch]

@cameronraysmith I've re-targeted to staging

I'm also not too sure how this fits in with the 26.11 release cycle #567567. I'd guess this would be classed as a breaking change which are currently frozen.

Review dismissed automatically

[cameronraysmith]

#579992 proposes to fix the excessive logging output issue prior to duckdb 2.0. However, if @jonasgloning agrees, we could consider reviewing this PR instead.

#579992 (comment)