From: doncatnip <gnopap@gmail.com>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: awesome: Add awesome-3.5
Date: Thu, 25 Aug 2016 19:26:11 +0200 [thread overview]
Message-ID: <20160825192611.759f04d0@gmail.com> (raw)
In-Reply-To: <87h9a8ucqw.fsf@we.make.ritual.n0.is>
On Thu, 25 Aug 2016 14:47:19 +0000
ng0 <ng0@we.make.ritual.n0.is> wrote:
I'm sorry, I just don't really know what to say about this as my
experience with hardening is rather non-existant. I can sure find out
how to disable dbus and submit another patch.
> ng0 <ng0@we.make.ritual.n0.is> writes:
>
> >> Works for me (written from inside a running awesome-3.5.9).
> >
> > ng0@shadowwalker ~$ awesome --version
> > awesome v3.5.9 (Mighty Ravendark)
> > • Build: Sun Mar 06 14:05:54Z 2016 for x86_64 by gcc version 4.9.3
> > (@) • Compiled against Lua 5.2.4 (running with Lua 5.2)
> > • D-Bus support: ✔
>
> Great, the joy of a limited font... Nevermind this message then for
> obvious reasons but rather take it as a note that dbus and hardening
> is something we need to watch in the future ;)
>
> > Having no dbus support will help with eventual hardening of Guix,
> > but why do we not have it in awesome?
> > And why would we we need it (dbus support) at all? I don't even
> > know why I used to build it with dbus support before. Works either
> > way.
>
next prev parent reply other threads:[~2016-08-25 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 1:09 [PATCH] gnu: awesome: Add awesome-3.5 gno
2016-08-25 9:22 ` ng0
2016-08-25 9:37 ` ng0
2016-08-25 9:59 ` ng0
2016-08-25 14:47 ` ng0
2016-08-25 17:26 ` doncatnip [this message]
2016-08-26 13:33 ` ng0
2016-08-26 15:19 ` doncatnip
[not found] ` <20160825172521.19de318e@gmail.com>
2016-08-25 14:50 ` ng0
2016-08-25 17:24 ` doncatnip
2016-08-30 6:56 ` Leo Famulari
2016-08-30 8:52 ` gno
2016-08-30 18:26 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160825192611.759f04d0@gmail.com \
--to=gnopap@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.