---
author: "Sérgio Cipriano"
date: ""
paging: "%d / %d"
---
##### INTRODUCING DH-MAKE-VIM
Tool inspired by dh-make-golang and gophian that automatically creates Debian packages for Vim and Neovim plugins.
---
# WHO AM I
- Brazilian.
- A vim/neovim user for about 8 years.
- Debian Developer (_cipriano@debian.org_).
- Mentor on the Debian Brazil community.
---
# WHY PACKAGE VIM PLUGINS?
---
# WHY PACKAGE VIM PLUGINS?
- Take some of the maintenance burden off users.
---
# WHY PACKAGE VIM PLUGINS?
- Take some of the maintenance burden off users.
- Many Neovim plugins don't have formal releases.
---
# WHY PACKAGE VIM PLUGINS?
- Take some of the maintenance burden off users.
- Many Neovim plugins don't have formal releases.
- The bug fixes and new features are mixed together making it harder to update.
---
# WHY PACKAGE VIM PLUGINS?
- Take some of the maintenance burden off users.
- Many Neovim plugins don't have formal releases.
- The bug fixes and new features are mixed together making it harder to update.
- Plugins sometimes expect Neovim versions that are not available on Debian.
---
# WHY PACKAGE VIM PLUGINS?
- Take some of the maintenance burden off users.
- Many Neovim plugins don't have formal releases.
- The bug fixes and new features are mixed together making it harder to update.
- Plugins sometimes expect Neovim versions that are not available on Debian.
- I already need to do this work every time I update my plugins or Neovim.
---
# WHY PACKAGE VIM PLUGINS?
- Take some of the maintenance burden off users.
- Many Neovim plugins don't have formal releases.
- The bug fixes and new features are mixed together making it harder to update.
- Plugins sometimes expect Neovim versions that are not available on Debian.
- I already need to do this work every time I update my plugins or Neovim.
- Packaging formalizes the process and makes the benefits available to everyone.
---
# WHY PACKAGE VIM PLUGINS?
- Take some of the maintenance burden off users.
- Many Neovim plugins don't have formal releases.
- The bug fixes and new features are mixed together making it harder to update.
- Plugins sometimes expect Neovim versions that are not available on Debian.
- I already need to do this work every time I update my plugins or Neovim.
- Packaging formalizes the process and makes the benefits available to everyone.
- Autopkgtest can help us test alongside the version of Neovim available in the archive.
---
# WHY I WORKED ON DH-MAKE-VIM?
---
# WHY I WORKED ON DH-MAKE-VIM?
- dh_make
---
# WHY I WORKED ON DH-MAKE-VIM?
- dh_make
- Similarity between packages
---
# WHY I WORKED ON DH-MAKE-VIM?
- dh_make
- Similarity between packages
- Repeated manual verifications
---
# WHY I WORKED ON DH-MAKE-VIM?
- dh_make
- Similarity between packages
- Repeated manual verifications
- Abcense of releases
---
# WHY I WORKED ON DH-MAKE-VIM?
- dh_make
- Similarity between packages
- Repeated manual verifications
- Abcense of releases
- It was fun.
---
# FEATURES
---
# FEATURES
1. Check if the software has already been packaged for Debian,
and whether it's in unstable, experimental or in the NEW queue.
---
# FEATURES
1. Check if the software has already been packaged for Debian,
and whether it's in unstable, experimental or in the NEW queue.
2. Check for an ITP/RFP, tell you about it.
---
# FEATURES
1. Check if the software has already been packaged for Debian,
and whether it's in unstable, experimental or in the NEW queue.
2. Check for an ITP/RFP, tell you about it.
3. Check for an existing Salsa repo with the name of the source package.
---
# FEATURES
1. Check if the software has already been packaged for Debian,
and whether it's in unstable, experimental or in the NEW queue.
2. Check for an ITP/RFP, tell you about it.
3. Check for an existing Salsa repo with the name of the source package.
4. Generate all the required files and only them.
---
# FEATURES
1. Check if the software has already been packaged for Debian,
and whether it's in unstable, experimental or in the NEW queue.
2. Check for an ITP/RFP, tell you about it.
3. Check for an existing Salsa repo with the name of the source package.
4. Generate all the required files and only them.
5. Opinionated, but customizable.
---
# FEATURES
1. Check if the software has already been packaged for Debian,
and whether it's in unstable, experimental or in the NEW queue.
2. Check for an ITP/RFP, tell you about it.
3. Check for an existing Salsa repo with the name of the source package.
4. Generate all the required files and only them.
5. Opinionated, but customizable.
- Choose between using a git commit as the package version or tags.
---
# DEMO
Create a package using the default options:
```
$ dh-make-vim make https://github.com/folke/which-key.nvim
```
---
# DEMO 2
Create a package without releases:
```
$ dh-make-vim make https://github.com/folke/which-key.nvim --no-watch-tag
```
---
# DEMO 3
Packaging a plugin with a custom source name:
```
$ dh-make-vim make https://github.com/kevinhwang91/promise-async.git --source-name promise-async
```
---
# DEMO 4
Example of a warning message for RFP bug:
```
$ dh-make-vim make https://github.com/sindrets/diffview.nvim
```
---
# DEMO 5
Example of a warning message for ITP bug:
```
$ dh-make-vim make https://github.com/kevinhwang91/nvim-ufo
```
---
# ALL AVAILABLE OPTIONS
```
$ dh-make-vim make --help
```
---
# PACKAGES THAT WERE MADE USING DH-MAKE-VIM
- neovim-alpha
- neovim-bufferline
- neovim-which-key
- neovim-toggleterm
- neovim-tokyonight
---
# NEXT STEPS
---
# NEXT STEPS
- Write more tests.
---
# NEXT STEPS
- Write more tests.
- Add option to choose a license.
---
# NEXT STEPS
- Write more tests.
- Add option to choose a license.
- Write a manpage for dh-make-vim.
---
# NEXT STEPS
- Write more tests.
- Add option to choose a license.
- Write a manpage for dh-make-vim.
- Add autocomplete.
---
# NEXT STEPS
- Write more tests.
- Add option to choose a license.
- Write a manpage for dh-make-vim.
- Add autocomplete.
- Add new custom options.
---
# NEXT STEPS
- Write more tests.
- Add option to choose a license.
- Write a manpage for dh-make-vim.
- Add autocomplete.
- Add new custom options.
- Add support for colorscheme plugins.
---
# NEXT STEPS
- Write more tests.
- Add option to choose a license.
- Write a manpage for dh-make-vim.
- Add autocomplete.
- Add new custom options.
- Add support for colorscheme plugins.
- Add more commands?