|02:32||lucascastro has joined IRC (firstname.lastname@example.org)|
|02:45||lucascastro has left IRC (email@example.com, Remote host closed the connection)|
|02:46||lucascastro has joined IRC (firstname.lastname@example.org)|
|06:43||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|07:33||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|09:10||kjackal has joined IRC (email@example.com)|
ok, let's see if i can get ltsp-docs back into debian testing...
Heh... just generate the lts.conf manpage once, and put it in the ltsp-server package :D
that's another strategy
i'd be up for that
you think that's the most important part of the docs?
it would certainly be easier to do it that way
|10:22||* alkisg checks what else is there in ltsp-docs...|
Ah, the manual, yeah its place should be in the wiki anyway
|10:45||Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)|
alkisg: now you've got me exploring the state of the art in low-formatting-markup to manpage generators
e.g. markdown to manpage, etc.
alkisg: so, yank the old ltsp-docs manpage, and kiss ltsp-docs goodbye?
Sounds great to me
ok. that's an actionable plan. :)
oh yeah, there's a bunch of commits tot he packaging for ltsp anyways that i hadn't yet uploaded
vagrantc: how do you feel about readthedocs.org? E.g. what if we put all the documentation in ltsp.readthedocs.org, epoptes.readthedocs.org etc?
(and deprecate the ltsp wiki, which is on an unmaintained server, full of spam etc?)
i'm generally not really excited about using arbitrary third-party services ... but i'm also not liking the unmaintained server...
alkisg: i'm thikning txt2man, fwiw
you pretty much write the input the way the output is supposed to look
i pretty much did man ./lts.conf.5.gz > lts.conf.txt and tweaked that a bit and now have something that's pretty workable
though it's kind of whitespace finicky
vagrantc: isn't .md a better format than .txt?
(to maintain a few pages, not just for lts.conf; to replace the wiki)
|12:01||zerkalo has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
Hmm I think github supports subdomain "hosting" too; maybe we could point wiki.ltsp.org to gitlab pages
alkisg: defines what you mean by better... the tooling to generate the man pages seems to require a lot more markup
but can't get the code block text to work...
|12:15||zerkalo has joined IRC (email@example.com)|
this is a mess.
vagrantc: for me nowadays it's important for documentation to be online, googlable etc. Manpages are fine for "app --help" entries, but not for how-tos etc
So I don't think manpages can be the base of a wiki or other documentation system; and I also like git; so... I feel like .md files are a good option
Also, imho, the lts.conf manpage should be autogenerated by doxygen-like comments in the source code, btw
So, tool --help => txt2man => manpage, lts.conf => doxygen style, all the rest => .md files...
*help2man, not txt2man, sorry
i've found ronn and go-md2man which actually i'm having better luck with than txt2man
we're already help2man for most of the commands, but lts.conf isn't a manpage
er, isn't a tool
at any rate, i need something sooner than later if we're going to have the lts.conf manpage in Debian's next release
i guess i can just dump the raw manpage
Sure, sounds fine
though i'd prefer to get it into markdown ... ronn pulls in more build-deps than go-md2man
seems faster too
er, go-md2man seems faster
both have been around a while, so backports should be workable
i'm learning towards go-md2man
i would have preferred txt2man, except that it got some of the variables randomly listed as man page sections
so far ronn and go-md2man seem to work reasonably with a dumped output from man with some manual adjustment
vagrantc: why do you need a text format at this point? What's wrong with using the existing lts.conf.xml and the man page that it outputs?
We don't need an automated build there, we can build lts.conf.xml into lts.conf.5 manually, and commit it when needed...
Isn't that just a single command that we can run?
|15:14||* alkisg successfully tried these:|
apt install --no-install-recommends xmlto
xmlto man lts.conf.xml
And, lts.conf.5 was ready...
|15:30||spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)|
alkisg: because dumping a manpage that's generated manually is not the "preferred form of modification"
alkisg: and i really can't stand the xml stuff
alkisg: that said, i have converted it!
we have a handful of fairly simple manpages in roff format ... but this wouldn't really be if we're using the docbook output
i'd like to move to formats that we might be more inclined to update :)
not that there's been much updating
vagrantc: if we were to update lts.conf, we'd update the .xml, like we "used to" do
Not the manually generated manpage
And, once we're ready to move it to code comments / doxygen style, we can migrate there
I'm not sure we need to migrate to maintaining a man format between that xml => comments migration...
i am perfectly happy to drop the whole .xml thing entirely
ok, np from me; I'll only work on that when it's time to put it in the comments anyway :)
gah. launchpad doesn't take modern ssh keys :/
so, i can only test ltsp on arm right now... heh.
gnome key manager also fails on modern SSH keys
if you passphrase protect it with some of the newer, stronger methods
|17:32||kjackal has left IRC (firstname.lastname@example.org, Ping timeout: 245 seconds)|
|17:33||kjackal has joined IRC (email@example.com)|
|17:36||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Remote host closed the connection)|
|17:47||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|18:07||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 252 seconds)|
|18:11||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
|19:38||spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Ping timeout: 268 seconds)|
|19:43||spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)|
|20:29||lucascastro has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|20:49||Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)|
|21:27||kjackal has left IRC (email@example.com, Ping timeout: 252 seconds)|
|21:43||lucascastro has joined IRC (firstname.lastname@example.org)|
|22:11||kjackal has joined IRC (email@example.com)|
|22:12||spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Quit: Leaving)|
|22:38||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)|
|23:18||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
|23:45||lucascastro has left IRC (firstname.lastname@example.org, Remote host closed the connection)|