summary refs log tree commit diff
path: root/pkgs/common-updater/scripts.nix
Commit message (Collapse)AuthorAge
* directoryListingUpdater: initJosé Romildo2022-10-01
| | | | Update a package looking for available versions in an html page
* treewide: makeWrapper buildInputs to nativeBuildInputsBen Siraphob2021-02-19
|
* treewide: stdenv.lib -> libPavol Rusnak2021-01-24
|
* common-updater-scripts: add mark-broken scriptMilan Pässler2020-04-16
|
* common-updater-scripts: add scripts to help update packagesJosé Romildo Malaquias2020-04-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - updateScript: A nix expression that can be used in passThrough to update a package - list-git-tags: A shell script to list available tags in a git repository - list-archive-two-level-versions: A shell script to list available versions in a web site in two levels: there is a page listing the available major.minor versions, and for each of them there is another page listings the patch level versions major.minor.patch. It is suitable for Xfce packages for instance. How the updater works: 1. collect the available versions from the source repository (using a script given as argument) 2. print the collected versions (for debugging) 3. (optionally) apply some transformation to the collected versions to make them compatible with the versions used in nixpkgs (for instance, tags in the Xfce git repository may be prefixed with the package name, and the prefix need to be removed) 4. sort the available versions in decreasing order 5. choose the first version that pass validation: - check if the version may be a development version - if the version IS unstable, skip it and give a warning about skipping a development version (for debugging) - if the version COULD BE unstable, take it and give a warning about taking a potential development version (for debugging) - if the version IS stable, take it 6. update the package version and checksum in its nix expression 7. print the git commands for adding the modified files and for committing the changes
* common-updater-scripts: clean upJan Tojnar2020-02-04
| | | | | | Fix issues reported by shellcheck and few other style issues. Though we need to ignore $systemArg complaints because Nix does not support passing --system as a single argument.
* treewide: use dontUnpackworldofpeace2019-07-01
|
* common-updater-scripts: Add file and system flagsJan Tojnar2019-03-02
| | | | | | | | | | | You can now optionally invoke update-source-versions with: * --system flag changing the host platform, to be passed dirrectly to Nix commands. This is useful for binary packages which have different sources for each platform. * --file flag allowing to change the file to be modified. This is useful for packages that offer multiple variants, listed in a different file than the derivation itself; e.g. packages.nix of Sublime Text 3. * --version-key, which is now a keyword flag instead of a positional argument.
* common-updater-script: fix error handlingtaku02017-05-19
| | | | diffutils is required for cmp command
* maintainers: Add script to patch version/sha256 in .nix filesTuomas Tynkkynen2017-02-19
Adds a script to help automatically upgrading packages: this one can patch name/version attributes like: version = "50.1.0"; name = "bc-1.06"; ... to the given version, and updates the sha256 hash to match. Usage is: update-source-version <attr> <new-version> [<new-source-hash>] where: - attr is the attribute path of the package - new-version is the version string to be patched in - new-source-hash is the optional sha256/etc. hash of the source. If not given, the script will automatically calculate it. This is added to a subdirectory where other useful scripts can be added in the future, like figuring out the newest version from a git repo or GitHub releases etc.