From 70960463c79d5b624a2f557f997b8062764bd601 Mon Sep 17 00:00:00 2001 From: Ryan Mulligan Date: Wed, 21 Mar 2018 21:57:19 -0700 Subject: [PATCH] update readme --- README.md | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index c56b619..e0cb587 100644 --- a/README.md +++ b/README.md @@ -1,18 +1,22 @@ # nix-update -Currently interesting files `ups.sh, up.sh, check-result.sh`. +[![Build Status](https://travis-ci.org/ryantm/nix-update.svg?branch=master)](https://travis-ci.org/ryantm/nix-update) -1. get a list of oudated packages +Scripts to try to update nixpkgs packages. Uses `hub` to automatically make PRs. + +# Instructions + +1. Clone this repo: +``` + git clone https://github.com/ryantm/nix-update +``` +2. Get a list of oudated packages and place them in a `packages-to-update.txt` file in the root directory of this repository. ``` git clone https://github.com/ryantm/repology-api.git cabal2nix --shell --hpack . > shell.nix && nix-build shell.nix && result/bin/repology-api > packages-to-update.txt ``` -2. Prepare a nixpkgs git repository where you want to do the updates. It expects `origin` to be where you want to push your updates. It clobbers any changes in that directory with `git reset --hard`. USE THIS ON A NEWLY CLONED REPO ONLY FOR THIS PURPOSE. -3. copy list of ones you want to update into `ups.sh` ARGUMENTS variable -4. delete update arguments that seem wrong. (Weird version strings, versions that don't seem like an update, the update version doesn't look like it would work with nixpkgs) -5. Be in the directory of your update git repository. run `ups.sh` if it succeeds, it will make commits and push updates to the `origin` remote! - +3. `./ups.sh` # prior work