Open cob-web-corner opened 1 week ago
Thanks for asking. Older versions for a project can be compiled by taking a branch out of the Technitium Library project from a commit that matches the same release data as that of the project's version commit being compiled.
Could you perhaps consider tags / releases? That would make maintaining the nixpkgs release (of Technitium DNS Server) easier.
Could you perhaps consider tags / releases? That would make maintaining the nixpkgs release (of Technitium DNS Server) easier.
Thanks for the suggestion. Will start adding tags and will add one for the current release.
To provide a possible solution to @FabianRig's request, I would tag/release according to your assembly version.
From there it might be easy to correlate each DNS Server released to an assembly version release. The same goes for other projects; this would allow for minimal branches/tags in this repo and bring some version organization/pinning to all Technitium projects
Just a suggestion, there's a million ways to do this
How do you handle version pinning against other projects like DNSServer? For example V13.0 was released today, how do you handle possible inconsistencies of compiling v13.0 against a possible future version of TechnitiumLibrary?