<mark_weaver>given that we are aiming for bit-for-bit reproducable (and thus verifiable) builds, then I wonder if we should be creating our own /dev from scratch anyway, instead of bind mounting it from the host system.
<mark_weaver>and that would solve this /dev/shm neatly, as a side effect.
<sdgfgdfgd>mark_weaver: Have you recieved a reply from RMS regarding FFmpeg?
<Steap>civodul: this seems stalled after "set-paths"
<mark_weaver>I decided not to ask him. It's not worth wasting his time about. I'm reasonably sure that I'm right about that particular point.
<sdgfgdfgd>mark_weaver: I believe that Jason thinks that you don't like the name because of MPEG-LA, but you seem to not like it because of MPEG. Right?
<mark_weaver>I'm not sure that I'm right about the overall decision, but I'm sure that MPEG is an organization worth disliking, and that this belief of mine does not demonstrate that I'm conflating MPEG and MPEG-LA.
<sdgfgdfgd>civodul: Have you read the logs regarding FFmpeg vs. Libav? What do you think?
<mark_weaver>Yes, the fact that I count as a (possibly weak) argument against ffmpeg (vs libav) that it promotes the name of a codec family and standards organization that makes free-software-hostile standards, seems to convince jason that I must be confusing MPEG and MPEG-LA.
<gzg>davexunit: I actually very-much like 3.10 -- that being said, I'm to used to my StumpWM, Emacs, Conkeror setup, to seriously consider something so drastically different.
<gzg>TaylanUB: A fair-amount, GTK is moving more and more into the usability paradigm in-which the GNOME project has taken to define.
<davexunit>I also enjoy gnome, though debian doesn't have 3.10 yet (or even 3.8?)
<davexunit>I just find that the term "usability" has come to mean "dumbed down"
<gzg>If we really "shun" GNOME from being officially promoted via GNU, I think Guile-WM looks promising for a general and flexible toolkit/environment -- especially if we can port it to a Wayland Compositor.
<davexunit>I like stumpwm, but I haven't had the time to configure it much. is there a place where I can find some extensions similar to emacs package repositories?
<gzg>davexunit: Well guile-wm is like a 1000x "worse" in that regard ... :^P Skim around for config files? I can post mine thus far, but it's like only half finished and I'm using waiting on guile-wm, for me to port it over as an excuse not to finish it. :^P
<davexunit>gzg: I would be happy to get in on the "ground floor" with guile-wm though because i'm a huge guile fan, but only lukewarm about common lisp.
<TaylanUB>Hrm, I'm realizing just now that WMs are more like X-interaction shells than window managers.
<gzg>davexunit: Well feel free to have at it! It's been about a month since there's been any work on it. I'd love to see and I probably will (need to pull myself out of this pity-pot first ...) to implement a ratpoison like wm in it.
<TaylanUB>For some time I lamented on the fact that they take a lot of WM-irrelevant functionality, like binding keyboard shortcuts, but now that I look at them as an X-interfacing tool it makes sense.
<TaylanUB>I should see if I can replace ratpoison with guile-wm some time.
<davexunit>my knowledge of X is low, but I did discover guile with the idea of writing a scriptable WM in Scheme.
<davexunit>so I'm glad to see that someone has already started the project.
<civodul>(and cgen = Guile, so yeaaah for MIPS ;-))
<civodul>Steap, mark_weaver: got it: mount(2) in build.cc succeeds, but mounts on the symlink's target, leaving the symlink unchanged; thus, after the call to chroot(2), we still have a dangling symlink
<mark_weaver>civodul: should I patch every Makefile.in that corresponds to an unpatched 'Makefile' in the failed build dir? or should I just patch the one in sim/testsuite and incrementally add more as I run into problems?
<mark_weaver>(the others are in ./etc ./bfd/po ./sim/common ./sim ./opcodes/po ./readline ./readline/shlib ./readline/doc ./readline/examples)