nits from pkgsrc packaging

[gdt]

Thanks very much for the README adjustment. I have added a package in pkgsrc (sysutils/seednaut), which will likely appear at https://pkgsrc.se/sysutils/seednaut in not very long.

This went very smoothly (pkgsrc has code to automatically package rust programs that use the normal idioms). A few tiny things I noticed that don't seem worth individual tickets (happy to do it if you want):

• There are license files at top level and in a license directory. This doesn't make sense to me.
• It was non-obvious what the project license is. I guessed AND (that it combined code from both), but from REUSE.toml I think it's OR. The README is silent.
• In the README, I suggest including iodé in the list.
• This says "CLI" but it seems more like "TUI". CLI implies to me that you run a program with arguments and it then does something, rather than something which is conceptually more like a GUI except it uses curses instead of gtk :-)
• There's no man page.

[Baltram]

Very much appreciate the pkgsrc package, thank you!

The duplicate license files are unfortunately necessary to satisfy both reuse and Licensee (which GitHub uses).

I have updated the README to include pkgsrc instructions and to mention iodé. It now also clarifies licenses and the fact that both TUI and CLI are present.
Generated man pages are now available under man/.

Let me know if anything is still off, especially regarding pkgsrc instructions.

Can you include the man pages in the package without me pushing a new version? Because on GitHub/crates.io the current changes would amount to just an updated README.

[gdt]

I could, because I could package a git hash instead of a tag. But pkgsrc, and many other packaging systems, have a norm of packaging only releases. I view the current culture of "just use git master" in projects as problematic. I don't mean to criticize a release followed by an improvement. It's just that some project have not had releases for many years, or have never had any.

I suspect you'll need a new version soon enough, as other people try this -- I think there's a lot of pent-up demand. I am not sure any actual people will use this in pkgsrc over the next month. So I'm inclined to let the package be until there is a release.

[Baltram]

Agree, it can wait.