IRC channel logs


back to list of logs

*davexunit pushed 'guix environment' patch
<davexunit>paroneayea: yeah, the reason the manual doesn't mention it is because it assumes you are building from a release tarball
<davexunit>developers need graphviz to build the manual, or they need to 'touch' the file that 'dot' would have created.
<paroneayea>davexunit: got it :)
<davexunit>ah good, it's actually documented in the HACKING file
<ph4nt0mas>good morning guix
<civodul>Hello Guix!
<civodul>the GHM video is on-line:
<Svetlana>hi there civodul
<civodul>sound is not very good, though
<Svetlana>i wanted to ask where i can find input text for translating the guix home page -- i don't think html markup is the way you wrote it by hand
<civodul>it turns out to be mostly written by hand, with server-side includes
<civodul>Svetlana: see on how to get it (with CVS!)
<civodul>translation would be nice
<Svetlana>ah so you do make it in html by hand ?
<civodul>yes, that's very low-tech :-)
<civodul>the non-software pages of are translated using GNUN
<civodul>for the software pages, it's up to each project
<civodul>so if you want we can start using GNUN
<Svetlana>it sounds a bit nice, but i could also handle .html pages equally easy, as i am currently only starting to learn to translate stuff at gnu
<Svetlana>it does sound nice for some things though -- as in, it does avoid some duplicate work of different translators and they can happily translate without knowing that html even exists
*civodul plays with "guix environment"
<civodul>sneek: later tell davexunit re "development deps": in "Installing Guix from Guix", we can't suggest running "guix environment guix", because the autotools would be missing
<sneek>Got it.
<Svetlana>how do i submit translation? i can email it to you directly right?
<Svetlana>as a .html file
<DusXMT>If I decide to package seamonkey (as the newest version of icecat is noticably slower on my machine), do I need to include additional freedom-enhancing features like including librejs by default? Or can I just package the upstream distribution?
<DusXMT>(Seamonkey is a mozilla-based browser that retains the look and feel of Netscape Navigator, which means the UI code is a lot lighter and more stable, and it even comes with an email client built in)
<civodul>Svetlana: please email it to the list as HTML, with server-side includes preserved
<civodul>DusXMT: i'm not sure, might be worth checking with
<civodul>because it's probably mostly the same code base
*civodul has to go, ttyl
<mark_weaver>DusXMT: unless something has changed recently with upstream SeaMonkey, I'm reasonably sure we wouldn't be able to use it as-is. Debian had "iceape" which removed non-free bits and also had to rename it because the Mozilla's trademark policy, but alas it seems that "iceape" lacks a maintainer at present, and is not in wheezy or jessie.
<mark_weaver>in GNU Guix, we aim to comply with the FSDG
<paroneayea>mark_weaver: excepting with manual license? ;)
<mark_weaver>paroneayea: what do you mean?
<mark_weaver>I'm talking about the GNU FSDG (Free Software Distribution Guidelines), not the DFSG (Debian Free Software Guidelines)
<DusXMT>mark_weaver: okay, in that case I'll just keep it as a local package, I'm far too noobish to take on something like maintaining iceape
<paroneayea>mark_weaver: ah, I got tricked by the similar looking acronymn ;)