<mthl`>davexunit: have you look to the website->sxml thing? <mthl`>you will notice that i stop trying formatting at some point when i realize that i can't make it pretty. <mthl`>I will continue the work tomorrow, if it's not done yet. ***tschwing_ is now known as tschwinge
<rekado_>hmpf, after repeated requests for a license declaration of a bioinfo tool I intended to package, the university department sent me a silly "standard academic license" with tons of restrictions on use, modification and copying. <rekado_>I find it especially annoying because they use LGPL code. <rekado_>is this even permitted under the terms of the LGPL? The code in question is compiled to objects and linked into the final executable. <rekado_>I miss the "infectiousness" of the regular GPL. <rekado_>I'm so disgusted by this "standard academic license". <civodul>"infectious" or "contagious" to describe copyleft is propaganda <civodul>it's propaganda as well, but the right one ;-) <Phlogistique>rekado_: (ianal) it's ok iff they provide a way to replace the LGPL code in the final executable with your own version <Phlogistique>(and ofc provide the source to their version of the LGPL code) <Phlogistique>both "infections" and "liberating" give the wrong idea that the licence is somehow able to move on its own and cover other programs <Phlogistique>whereas the reality is that developpers chose to accept a licence when they are using a GPL or LGPL product to build their own product <rekado_>What I intended to say was, however, that I'm sad that the license of the code they include does not override their ridiculously restrictive terms for the combined work. I see the restrictive license as the disease, not the virus delivering the cure. <rekado_>(In general I think that bacteria and viruses have a needlessly terrible reputation.) <rekado_>what I find somewhat disturbing about this is that the license isn't even published. I wonder if the people who have contributed to this piece of software are aware of its license. <rekado_>I usually assume "all rights reserved" unless shown otherwise, but the people I've met seem to think "it's on github/bitbucket, so it's 'open source'". <rekado_>yes; but I suppose the term "open source" is vague enough to make it seem obvious that what is published is "open source". <rekado_>I don't like these terms that prevent thinking about concepts clearly. <rekado_>anyway, I have lost all interest in this piece of software. <civodul>what university was that, if that's something you can say? <civodul>iyzsong: i'm taking the $GUIX_PROFILE approach in the end <rekado_>civodul: I was wrong. It's actually a division of a publicly funded health care provider in British Columbia, not a university. <rekado_>I can pass "--listen=some-socket" to guix-daemon, but how can I tell the guix client to use the specified socket file instead of the one in localstatedir? <civodul>rekado_: clients honor $GUIX_DAEMON_SOCKET <Juhani>git is THE distributed version control system <rekado_>recently an acquaintance was complaining about not being able to create private git repositories for personal use. (In their mind git = github.) <civodul>mthl: no i hadn't, but that looks good <civodul>i think davexunit was looking at it too <davexunit>mthl: feel free to carry on, I haven't done any work on this. <phant0mas>I think it's time I start making modifications in make-bootstrap.scm to try to produce the hurd bootstrap-tarballs <mthl>have you any opinion on the indentation? <davexunit>does anyone know how to deal with cmake scripts that search in hardcoded directories for headers and libs? <davexunit>and preventing me from building some software <civodul>mthl: yeah, whatever pretty-print or emacs produces <civodul>davexunit: i don't know, but probably there are other packages already doing that? <civodul>mthl: ideally you could make one module per web page <civodul>like: (define-module (www) #:export (main-page)) (define main-page '(html ...)) <civodul>and then similarly for (www download) <davexunit>civodul: I haven't seen anyone else deal with it. <civodul>davexunit: i suspect iyzsong would know the answer <iyzsong>oops, you're mean the FindX11.cmake from cmake package. Nope, I don't know how it works.. <davexunit>passing -DX11_FOUND=1 to cmake has helped somewhat <davexunit>along with another flag that the FindX11 script sets <davexunit>though, to enjoy this program I just built, I need to fix mesa... <vmlinuz88>davexunit Are there any suggestions/tips for running GuixSD in a vm? <davexunit>vmlinuz88: I can't think of anything specific to that <davexunit>I use qemu/kvm and generate my VMs with 'guix system vm' for quick tests (temp fs, shared store) <vmlinuz88>davexunit Where is the vm template file located? <cehteh>a 'guix locate ... ' would be nice somtimes :D <cehteh>really i am not sure yet, but locating things in the store, find the package definitions etc <cehteh>prolly a 'guix apropos' would be more approbiate. as being new to guix i have some problems to figure out where things are defined <davexunit>'guix package' tells you where package definitions are <davexunit>for example, 'guix package -A emacs' will give source locations for all emacs packages <vmlinuz88>davexunit: what is the difference between gnu-system.scm and guix.scm in the build-aux/hydra/ directory? <cehteh>havent played with guix these days, setting up my quadcopter :D <cehteh>will be back on guix in a few days <davexunit>vmlinuz88: I don't know, those are used for our build farm, it seems. <davexunit>seems that guix.scm is for the guix itself, while gnu-system.scm is for the packages <civodul>mark_weaver: it's to do a 'make distcheck' of Guix itself <mark_weaver>well, I've never seen it succeed, but I suppose I rarely look :) <vmlinuz88>what file do I use for a guix system disk-image argument? <davexunit>vmlinuz88: neither of those files you were wondering about have anything to do with OS configs. <vmlinuz88>davexunit I figured as much, based on what was mentioned about them above. <vmlinuz88>could something like configuration-template.scm be used? <davexunit>vmlinuz88: there's build-aux/hydra/demo-os.scm <civodul>mark_weaver: could it be a non-determinstic issue? <mark_weaver>civodul: it would be very helpful if the relevant test log(s) were printed when 'make check' fails, especially on MIPS where we have so little available build capacity. <mark_weaver>it's over an hour of build time wasted, which now has to be repeated to recover the test log <mark_weaver>and it seems fairly common to have guix test failures on non-intel platforms <civodul>it's hard for me to tell if it's "fairly common" if there are no reports, hint hint <mark_weaver>heh, well, I've chosen to just work on fixing the bugs rather than report a bug that no one else is likely to work on <mark_weaver>and part of the issue is that by the time I know enough details to file a report, I already know how to fix the bug. <mark_weaver>most of the work is rebuilding guix to recover the test log <mark_weaver>and I've turned every decent MIPS box I have access to into a hydra build slave <vmlinuz88>davexunit: when building a disk-image, I get an error that says "Could not access KVM kernel module: Permission denied." <davexunit>vmlinuz88: you need permissions to access /dev/kvm <davexunit>as a hack, a lot of us just 'chmod 666 /dev/kvm' <civodul>yeah i think the manual has a footnote on that topic ;-) <civodul>i've just pushed the thing to build the profile's profile file (sic) <mthl>"Make check" doesn't succeed on my machine <taylanub>mthl: could you paste the contents of profiles.log? <taylanub>(I was confused because I thought I have the latest master and couldn't find the test) <taylanub>mthl: when you open the file tests/profiles.scm and change the string "source " to ". " it will probably succeed <taylanub>I'm preparing a patch, assuming that is the bug. (it could also be that the test should explicitly use GNU Bash instead of any /bin/sh, I can't tell right now.) <mthl>taylanub: thanks for looking into it! <mthl>"make check" is running again but the test fails with ". " too <mthl>i annotate the previous one with only the interesting part <taylanub>can you paste the make check output too? (where it was saying "/bin/sh: 1: source: not found") <paroneayea>forgot to add #guix to my autojoins, corrected :) *taylanub tries 'make check' with no ~/.guix-profile in any *PATH variables and /bin/sh set to dash <taylanub>ah, found the problem: dash's output for set(1) is like FOO='value' with the single quotes <phant0mas>civodul: added a macro in base.scm so make-bootstrap.scm will choose the right glibc based on target system <phant0mas>and made sure it works with everything else :P <phant0mas>now I am working on actually making guix build --target=i686-pc-gnu bootstrap-tarballs to produce the tarballs <civodul>taylanub: maybe that test should just use Bash, actually <civodul>the syntax of the profile's etc/profile is not POSIX Bourne shell <civodul>it's rather Bash, but zsh supports it too <civodul>the macro to select the right libc is a good idea <taylanub>civodul: hm, it actually worked with dash after fixing a second bashism. by the way there was also a third problem that was sh/bash-unrelated; I just sent a patch fixing all three. <civodul>ok, well even better if we can get it to work with dash! <phant0mas>civodul: even though "guix build gnumach-headers" works just fine to produce the cross-toolchain, when I try "guix build --target=i686-pc-gnu gnumach-headers" to build them using that toolchain it fails at configure <civodul>phant0mas: probably due to "--build=i686-pc-gnu" <civodul>"--build=i686-pc-gnu" means "the build machine runs GNU/Hurd", which is not the case <civodul>so here maybe configure thinks it's not cross-compiling because host = build <civodul>so maybe you can conditionalize the --build hack on whether it's being cross-compiled <civodul>like (if (%current-target-system) '() '("--build=i686-pc-gnu")) <phant0mas>btw tomorrow I will report to both mailing list what I did this week, so we can keep everyone up to date and happy :-) *davexunit attempts to fix nouveau in mesa package <davexunit>can't play any video games on guixsd without working 3d accel <davexunit>the mesa package got cleaned up quite a bit and made this easy. :) <davexunit>minetest runs at an acceptable speed now. ;) <davexunit>civodul: a change to mesa will affect a good number of packages, I think. should I push the fix to master or core-updates? <mark_weaver>davexunit: oooh, nice! I think it should be built on a separate branch <bavier>davexunit: 'guix refresh -l mesa' says 206 packages *davexunit always forgets about 'guix refresh' <bavier>mark_weaver: in this case it should be fine <bavier>mark_weaver: I've done a bit of work to increase the reliability, but it's still too slow to be acceptable IMO <mark_weaver>it doesn't take into account any implicit inputs, in this case the gtk+ implicit input added the gtk/glib build system <mark_weaver>I remember that mesa causes a lot of rebuilding. imo it should be done on another branch <davexunit>yeah, anything that uses OpenGL needs to be rebuilt now. <bavier>mark_weaver: I see, I didn't know about gtk+ <davexunit>so if I make the branch, will someone else do whatever needs to be done such that hydra builds it? <davexunit>this means I should have webgl support in icecat now :) <davexunit>I'm not sure what to do, but I need to figure out a way to get a more up-to-date mozilla browser.