<feed xmlns='http://www.w3.org/2005/Atom'>
<title>dotfiles/dot_config/nvim/create_nvim-pack-lock.json, branch master</title>
<subtitle>My linux config and rc files</subtitle>
<id>https://git.sommerfeld.dev/dotfiles/atom/dot_config/nvim/create_nvim-pack-lock.json?h=master</id>
<link rel='self' href='https://git.sommerfeld.dev/dotfiles/atom/dot_config/nvim/create_nvim-pack-lock.json?h=master'/>
<link rel='alternate' type='text/html' href='https://git.sommerfeld.dev/dotfiles/'/>
<updated>2026-05-13T12:43:09Z</updated>
<entry>
<title>chore(nvim): stop tracking pack lockfile</title>
<updated>2026-05-13T12:43:09Z</updated>
<author>
<name>sommerfeld</name>
<email>sommerfeld@sommerfeld.dev</email>
</author>
<published>2026-05-13T12:43:09Z</published>
<link rel='alternate' type='text/html' href='https://git.sommerfeld.dev/dotfiles/commit/?id=2f8796ea38d9b463eededd0bbce9af291c086e7b'/>
<id>urn:sha1:2f8796ea38d9b463eededd0bbce9af291c086e7b</id>
<content type='text'>
The seeded lockfile offered little value for a single-user setup: fresh
bootstraps will resolve version specs at install time, and any meaningful
pinning is already expressed in init.lua's vim.pack.add() specs. Added
an explicit .chezmoiignore entry so the runtime file doesn't show up as
drift.
</content>
</entry>
<entry>
<title>chore(nvim): seed pack lockfile with create_ prefix</title>
<updated>2026-05-13T12:43:09Z</updated>
<author>
<name>sommerfeld</name>
<email>sommerfeld@sommerfeld.dev</email>
</author>
<published>2026-05-13T12:43:09Z</published>
<link rel='alternate' type='text/html' href='https://git.sommerfeld.dev/dotfiles/commit/?id=b4db2d4a137f31fe81c4bd1a1d2ca3407401882d'/>
<id>urn:sha1:b4db2d4a137f31fe81c4bd1a1d2ca3407401882d</id>
<content type='text'>
The file is owned by vim.pack at runtime — tracking it causes constant
chezmoi drift on every plugin update. The create_ prefix writes it once
on fresh machines and leaves it alone after. Manually chezmoi re-add
when you want to snapshot a known-good revision set.
</content>
</entry>
</feed>
