Closed a1lu closed 3 years ago
wow, thanks a lot
Todos
* are we section 1 or section 8
I would say section 8.
* do we want to keep the .md file and the man page
I guess the source repo should have the .md file only, and we can compile the man page in the PKGBUILD. If you agree, remove the man page and I'll update the PKGBUILD
* create a `doc` dir?
no need for a single file. if we grow more docs, then we can think about it.
* list all configuration options in `OPTIONS`?
the man page should be as comprehensive as possible. I'm fine to merge it even in a lesser form, and we can evolve it from there.
* do we want to keep the .md file and the man page
I guess the source repo should have the .md file only, and we can compile the man page in the PKGBUILD. If you agree, remove the man page and I'll update the PKGBUILD
We can do this, but that would add the go-md2man package as a build dependency only to create the manpage.
We can do this, but that would add the go-md2man package as a build dependency only to create the manpage.
it's a 2.7mb compiled package from [community], without any dependencies, and we'll be adding it as a makedeps - I say it's fine.
Alright, I think this commit should fix all open issues. If you are fine with it I'll squash them and remove the WIP tag.
I squashed the commits and it's fine to merge from my side.
ps. you don't need to squash the commits, in the end I'll squash-merge them
ps. you don't need to squash the commits, in the end I'll squash-merge them
Good to know github does this too. I'm more used to gitlab.
thanks
I would like to propose this man page.
I wrote it in markdown (
secure-boot-man.md
) and generated thesecure-boot.1
man page with go-md2man (from community repo)Todos
doc
dir?OPTIONS
?