From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH]: xfce4-power-manager: new variable
Date: Mon, 7 Mar 2016 23:37:38 -0500 [thread overview]
Message-ID: <20160308043738.GA11420@jasmine> (raw)
In-Reply-To: <87si02s91g.fsf@gnu.org>
On Mon, Mar 07, 2016 at 02:38:03PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > On Thu, Dec 03, 2015 at 03:04:55PM +0100, Florian Paul Schmidt wrote:
> >> Hi,
> >>
> >> attached is a patch for a first stab at packaging xfce4-power-manager. Since
> >> I used a different package as a base for this one there might be some
> >> unneeded inputs. I wonder if you guys have a tip for creating a little
> >> scheme snippet that would try all combinations of inputs to determine the
> >> minimal set for which ones the package build still succeeds? ;) [lazy flo]
> >
> > The potential issue with this approach is that a lot of software will
> > build successfully even if some dependencies are missing. And then it
> > will fail at runtime, sometimes only in certain scenarios. Not that I
> > haven't thought about doing the same thing... :)
> >
> > Ideally each program would have a test suite that exercised every code
> > path. Maybe AFL would be useful there? That sounds expensive but for
> > very complex systems, it would be worth it, because in my limited
> > experience packaging software, I have found that many upstream
> > developers are not aware of the dependency graph of their software. It's
> > fun to send them the output of "guix graph".
>
> Looks like the xfce4-power-manager patch fell through the cracks. Leo,
> could you maybe do a final polishing pass and commit it?
Sure. I separated the addition of the package and its use in the xfce
meta-packaged into two patches.
I know you asked me to commit, but since I don't have a system where I
can test Xfce with power, I'm submitting the patches.
Does anyone want to test? It does pass its test suite.
I will go ahead and commit the patches if you confirm it's okay without
having tested them.
next prev parent reply other threads:[~2016-03-08 4:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 14:04 [PATCH]: xfce4-power-manager: new variable Florian Paul Schmidt
2015-12-03 19:01 ` Leo Famulari
2016-03-07 13:38 ` Ludovic Courtès
2016-03-08 4:37 ` Leo Famulari [this message]
2016-03-08 4:38 ` Leo Famulari
2016-03-15 14:20 ` Ludovic Courtès
2015-12-03 21:40 ` Florian Paul Schmidt
2015-12-03 21:43 ` Florian Paul Schmidt
2015-12-04 23:03 ` Florian Paul Schmidt
2015-12-06 21:51 ` Ludovic Courtès
2015-12-06 22:13 ` Florian Paul Schmidt
2015-12-04 17:16 ` Andreas Enge
2015-12-04 19:02 ` Florian Paul Schmidt
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160308043738.GA11420@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).