> Where is the VCS?

There isn't one, at least publicly. The author exports everything from SVN for each release, even though I pointed him towards git-svn for github two years ago.

What's painful is that the liblfds API is completely renamed for each release, even minor ones -- all functions prefixed by the version number [1]. According to the author, the intention is to facilitate concurrent use of different liblfds versions. That might be forgivable for major releases, but not minor ones, IMHO.

Overall, liblfds worked well (at least the queue, which was the only part I used) until version 6.0 was back-ported with the API rename and totally broke my code. After a couple emails with the author about this, I stopped using the library because I found the release strategy disagreeable enough to be a dead-end.

[1] There are ways to sanely achieve this effect with macro expansion of function names, and still maintain a consistent API with #define aliasing... the author didn't seem interested in supporting this.

Good question. The GitHub account is odd. There appears to be a new repository for each release.

https://github.com/liblfds?tab=repositories

With all due respect, frames on the website? Creating a new repo for version releases? I would like an explanation from the author.

Many people judge books by their cover - I say let's see the code. But superficial things like that do matter in people's perceptions.

edit: below, frames.

I assume you mean frames and not iframes.