# zigford.org

About | Links | Scripts
Sharing linux/windows scripts and tips

### Trying out a pull request

October 06, 2019 — Jesse Harris

You've received a pull request on your repo. Before merging you want to see what it looks like in your code base. Perhaps you will run some manual test or some diffs from the command line here and there.

Read more...

### Making a release on GitHub

August 20, 2019 — Jesse Harris

Today's journey is using `git` and `github` to release PwshBlog The following are my notes on the matter.

Read more...

### Git - Working with branches

August 06, 2019 — Jesse Harris

In this quick article, I will:

- quickly create a branch on a git repository.
- make some commits
- push them to a remote branch
- clone to a new location (to simulate working on another machine)
- merge the new branch to master
- delete the local and remote branches

Read more...

### Using the latest vim on Gentoo

May 22, 2018 — Jesse Harris

Most people (including myself until recently), think of Gentoo as a bleeding edge source distribution. This is pretty far from accurate as most packages marked stable are quite out of date. And even if you decide to accept all unstable packages by adding:

            ACCEPT_KEYWORKS="~amd64"

to your make.conf file, you will likely be a bit disappointed when you can't get the latest gnome bits.

As my last post indicated, I'm a bit of a vim user and I want to have the latest vim on all my machines (Windows at work, WSL/Ubuntu 18.04 on the Windows box, and Gentoo at home). To that end, here is the simple thing you need to do to get the latest Vim on Gentoo:

# Overview

1. Add a special keyword to vim's ACCEPT_KEYWORDS var
2. Unmerge existing vim
3. emerge the new vim

## Keywords

Newer versions of portage allow /etc/portage/package.keywords to be a directory with simple files so that you can seperate files for seperate packages. Now, lets check if it is a file or dir and convert it if it is a directory.

        cd /etc/portage
        if test -f package.keywords; then
            mv package.keywords keywords
            mkdir package.keywords
            mv keywords package.keywords/
        fi

And now, lets use the special keyword for the vim package which will allow ebuilds from github

        echo app-editors/vim "**" > package.keywords/vim
        echo app-editors/gvim "**" >> package.keywords/vim
        echo app-editors/vim-core "**" >> package.keywords/vim

## Unmerge existing vim

        emerge --unmerge app-editors/vim app-editors/gvim

## Merge the new vim

        emerge app-editors/vim app-editors/gvim

## Final thoughts.

This is the way I did it, but thinking about it now, it may be unnessecary to unmerge vim. You could probably get away with running emerge --update vim gvim

Tags: gentoo, vim, git, ebuild