Opened 2 years ago
Closed 2 years ago
#5110 closed defect (fixed)
vim: .spl file location has moved
Reported by: | pierre | Owned by: | lfs-book |
---|---|---|---|
Priority: | normal | Milestone: | 11.3 |
Component: | Book | Version: | git |
Severity: | normal | Keywords: | |
Cc: |
Description
From a mail by Barry Allard on lfs-dev:
New: https://github.com/vim/vim/tree/master/runtime/spell/ Reference: README at https://ftp.nluug.nl/pub/vim/runtime/ (ftp.vim.org. 4563 IN CNAME ftp.nluug.nl.) --- OBSOLETE: This directory is old and is no longer being updated. Use the runtime files from github instead: https://github.com/vim/vim/tree/master/runtime
Actually, tt looks like the "spell" subdirectories do not contain .spl files anymore, and they have to be generated using the procedure in the README.txt file (it seems the .spl files for English are already present in the spell directory, not the /spell/en subdirectory). Also, the directory "runtime/spell" is included in the vim tarball. Since this directory does not change much, and we update regularly to recent git versions, I think mentioning the github spell directory is not necessary. But we should maybe give a recipe for generating the non English .spl files.
Change History (8)
follow-up: 2 comment:1 by , 2 years ago
follow-up: 3 comment:2 by , 2 years ago
Replying to Xi Ruoyao:
By the way, should we just download the release from GitHub instead of uploading one onto anduin? Could someone recall why we started to use anduin in the first place?
At one time vim was not on github, and getting releases or patches was complex. ISTR I once tried to get a patch to fix an issue, but it would not apply (odd format). From my notes in January 2019 I downloaded a tarball from a mercurial repository at bitbucket.org by using hg clone and hg archive.
I have just now had a quick look at github but failed to find a releases page for versioned tarballs. Any link ?
comment:3 by , 2 years ago
Replying to ken@…:
I have just now had a quick look at github but failed to find a releases page for versioned tarballs. Any link ?
The point version tar.gz tarballs can be found under "tags"...
follow-ups: 6 7 comment:5 by , 2 years ago
The problem with the github tags is that they are updated so often that the url we put into the book rolls off the first page and is no longer correct. Using anduin makes the url permanent.
comment:6 by , 2 years ago
Replying to Bruce Dubbs:
The problem with the github tags is that they are updated so often that the url we put into the book rolls off the first page and is no longer correct. Using anduin makes the url permanent.
I think I may have confused currency issues with the URLs in the book. The URL should not be affected by the tags page.
I'll also note that we reference https://github.com/vim/vim/tags in the book, but github seems to want to redirect to https://github.com/vim/vim/releases. We need a trailing / in that url if we keep it in the book.
comment:7 by , 2 years ago
Replying to Bruce Dubbs:
The problem with the github tags is that they are updated so often that the url we put into the book rolls off the first page and is no longer correct. Using anduin makes the url permanent.
https://github.com/vim/vim/archive/v8.2.0001/vim-8.2.0001.tar.gz is still valid today.
comment:8 by , 2 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in trunk. Switching download URL is a separate issue.
By the way, should we just download the release from GitHub instead of uploading one onto anduin? Could someone recall why we started to use anduin in the first place?