-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Overhaul the NuGet packaging infrastructure and the way the Core bina…
…ries get acquired. (#146) * Start writing an MSBuild script that creates NuGet packages for the core. For now it downloads the artifacts from GitHub Releases. * Support creating the native packages. * Support creating the metapackage. * (REMOVE BEFORE MERGE) Add a temporary MyGet feed for the TileDB native packages. * Use the TileDB Embedded page for the project URL in the native packages. * Use the `TileDB.Native` NuGet package and remove the nuspec of `TileDB.CSharp`. * Set `UseCurrentRuntimeIdentifier` in the executable projects. * Restore the template packages. And add a property to them that seems to save time. * Remove the ValueSeparator hack. * Remove the "Install/Download tiledb" steps from CI. And disable fail-fast in the Run-Tests action matrix. * Remove all CI jobs except of Run-Tests. Now that we don't use a nuspec to pack the C# library there are little reasons to specifically test it with a packed NuGet package. The Release job also went away; it would upload the 0.0.0-local package. We need a dedicated release workflow. * Remove RollForward from TileDB.CSharp. It does not apply to libraries. * Update package metadata and move them to a dedicated file. I had originally removed the nuspec files from the native packages but changed my mind for aesthetic reasons since they generate an empty .NET Standard 2.0 dependency group. * Add support for generating development editions of the native packages. They have SemVer 2.0 versions that identify the branch. * Enable Central Package Management with package source mapping. And support changing the native package under a different name in development builds. * Add release notes in the packages. * Refactor the nightly build workflow to use native development NuGet packages. The core is built in separate jobs and not once for each .NET version. * Update the repository README and add a package README. * Require `Version` and `VersionTag` to be specified. Make the version tag optional for development builds. And fail if no native binaries were found in development builds. * Add a README describing the native NuGet package generator. * Demand Core version 2.12.x. * Warn when building an RID-agnostic executable that uses `TileDB.CSharp`. * Remove the RID-specific build instructions in the metapackage's description. This package is not intended to be directly referenced by the average developer, at least not without `TileDB.CSharp`. * Remove the MyGet feed; we are now using the official TileDB binaries from NuGet. * Use MSBuild's custom item separator feature instead of a `string.Replace` hack.
- Loading branch information
1 parent
5c217a9
commit 6f9fc19
Showing
33 changed files
with
464 additions
and
920 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.