IRC chat logs for #ltsp on irc.libera.chat (webchat)

Request log from specific day:

Channel log from 6 December 2018 (all times are UTC)

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