<mark_weaver>I built GNOME 2.32 by hand on my YeeLoong, on my home-grown distro based on Cross [GNU/]Linux from Scratch, and I remember it being a huge project. and that was even when not putting everything into /gnu/store/
<mark_weaver>calling it "the GNU distribution" or even just "the GNU distro" would be better, because it doesn't suggest that it's the name of it.
<tadni>mark_weaver: Is that not worse, because then it implies it's the official GNU distro?
<mark_weaver>when you say things like "GNU Distro"'s status, it makes it sound like a name, and it makes me feel like you're trying to establish "facts on the ground" even though we've rejected the name.
<mark_weaver>it means when you try to establish something as a fact, often by underhanded means, even when no formal or legal decision has been made.
<tadni>Also, the name that was rejected was "Gnudist" which is different than saying "Gnu Distro" while I get that may be a bit confusing to some people thinking the name of the distro is just GNU ... saying "the GNU distro" I think is worse, because it establishes it being an officially pushed variant, from the GNU project.
<tadni>Feel free to continue this convo, I'll leave the chat open -- but I've been up about 22 hours and don't want to mess up my sleep schedule anymore.
<mark_weaver>well, I'm just following the terminology used in the Guix manual itself, so at least it's not my unilateral choice
<mark_weaver>I didn't realize that we already had asciidoc packaged. I wonder why we're not using it as an input to 'git' to build its documentation.
<mark_weaver>I will grant that there are two problems here that can happen. Saying things like: "GNU Distro"'s status, gives a false impression that it's a chosen name. Saying things like "the GNU distribution" doesn't have that problem, but it _does_ imply that it's official.
<rekado_>I hope I've done this all right. I only rarely have to use ChangeLog style in commit messages and the ubiquity of github makes me rarely use git format-patch.
<rekado_>I noticed that Emacs likes to format the code a wee bit differently; for example, it doesn't align the keys in arguments properly. How do you convince Emacs to align the code such that keys are lined up?
<davexunit>I correct it manually because I don't know of a way to make it indent properly.
<rekado_>civodul: I actually like Texinfo. The HTML output probably misses a search feature and a nicer default style sheet (really just to limit the width of paragraphs for readability) to make it "web-friendly".
<rekado_>I'm a bit surprised that org-mode is pushed as an alternative format --- as if esr's premise was not in dispute.
<civodul>rekado_: yeah the default style sheet for Texinfo should be improved
<rekado_>I think a massive improvement would be to limit the maximum paragraph width dependent on font size to get readable line lengths.
<mark_wea`>rekado: you can't delete things from /gnu/store manually without causing lots of trouble. there's an sqlite database that says what's in /gnu/store, and beyond that, if "guix gc" didn't already delete something, there must be other things in the store that refer to it.
<mark_wea`>rekado: there may be some more clever way to fix things, but in the past when I've done that I've had to remove *all* of /gnu/store and $PREFIX/var/guix and start from scratch.
<mark_wea`>rekado: the proper way to delete individual items from the store is "guix gc --delete /gnu/store/..."
<mark_wea`>(which will refuse if there are any references left, but that's life)
<rekado_>mark_weaver: yeah, I learned this the hard way :)
<mark_weaver>this is terrible. my new ISP is very frequently dropping my TCP connections. it's not only dropping me off of IRC every time I turn around, but also the MIPS builds are frequently failing the SSH connections are getting lost in the middle of builds.
<mark_weaver>in order to become a technical contact for my ISP, I was asked to agree to a very long legal agreement. at the top, it said that I had to agree not only to the current agreement, but also to any changes they might make in the future. *grump*
<mark_weaver>I suppose the person who signed up for this service also had to agree to it, but that wasn't me.
<mark_weaver>I see this more and more often these days. google also asked me to sign something like that to become a mentor for GSoC, and I refused.
<mark_weaver>yep, and it seems like almost everyone is willing to click "agree" anyway.
<mark_weaver>(usually without reading what they're agreeing to, I suspect)
<Sleep_Walker>I'm afraid that with the amount of legal text and no experience in law it is impossible to even check
<mark_weaver>not impossible, but expensive to check competently. still, one could at least try to read and understand, before signing or clicking "agree". it makes me crazy to think about how many people sign away their rights like this.
<mark_weaver>it makes life very difficult for those of us who don't want to do that.
<mark_weaver>five of them are at the top of the list in top sorted by memory. the top is using about 1 gig of virtual memory, 745 megs resident. the others are using a lot too. not sure how much is shared between them.