On Mon, Jan 15, 2018 at 10:08:56PM -0500, Mike Gerwitz wrote:
> On Mon, Jan 15, 2018 at 09:07:45 +0100, Pjotr Prins wrote:
> > GNU Guix, however, by virtue of being a GNU project is hampered by its
> > free software credentials.
>
> "hamper" isn't a good word to use to describe the FSDG:
Shackled
Hello,
Leo Famulari skribis:
> On Wed, Jan 10, 2018 at 05:39:59AM +0800, Alex Vong wrote:
>> I have an idea. Should we add a news entry to Guix blog[0] summarizing
>> all the above? For example, we can advice users to install noscript and
>> turn off javascript by default and only enable it on t
One thing we ought to organise is recording video at the event. Who
would be interested in helping out with that? And who could supply
some hardware? I don't think we have to go for professional quality,
but it should be a bit more than a phone recording.
Pj.
Leo Famulari skribis:
> On Tue, Jan 09, 2018 at 06:10:02PM -0500, Mark H Weaver wrote:
>> Marius Bakke writes:
>> > Katherine Cox-Buday writes:
>> >> I am also interested -- more from a philisophical perspective -- how
>> >> GuixSD and GNU squares with these kinds of security updates.
>> >
>> >
Marius Bakke skribis:
> Chris Marusich writes:
>
>> By "Guix publish works over mDNS," I mean that if I publish substitutes
>> on one machine in my network, then other machines on my network will
>> discover the publishing endpoint via mDNS and use it transparently like
>> any other substitute s
Catonano skribis:
> In G-golf ( https://git.savannah.gnu.org/cgit/g-golf.git ) in the
>
> g-golf/init.scm
>
> file, there's this line
>
> (define %libgirepository (dynamic-link "libgirepository-1.0"))
If you’re writing a package for G-Golf, the solution is to substitute
"libgirepository-1.0" wit
Hi Pjotr,
> One thing we ought to organise is recording video at the event. Who
> would be interested in helping out with that? And who could supply
> some hardware?
I could bring a camcorder with a stand. Surprisingly, I don’t have a
microphone. We’d need one with a 3.5mm jack. The integrate
On Tue, Jan 16, 2018 at 12:10:53 +0100, Ludovic Courtès wrote:
> Should GuixSD nevertheless provide a mechanism to support microcode
> updates, while not steering users to particular proprietary microcode?
> Just like Linux-libre (attempts to) support loading of proprietary
> firmware at the user’s
