From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: inxi and inxi-full Date: Mon, 16 Apr 2018 12:46:51 +0530 Message-ID: <877ep7d3j0.fsf@gmail.com> References: <87h8p0wb6m.fsf@gmail.com> <87woxwkypg.fsf@gmail.com> <874ll09kn6.fsf@gmail.com> <87po353efj.fsf@gmail.com> <877epcesqb.fsf@gmail.com> <877epcq0mg.fsf@gmail.com> <87h8og1hgi.fsf_-_@gmail.com> <87fu40pcky.fsf@gmail.com> <87woxb22o3.fsf@gmail.com> <874lkfpxfu.fsf@gmail.com> <87tvsfzo4r.fsf@gmail.com> <8736zzps94.fsf@gmail.com> <87in8vws4e.fsf@gmail.com> <87y3hroc7m.fsf@gmail.com> <87o9iml333.fsf@gmail.com> <87o9ijab7b.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49195) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f7yNo-0002A3-94 for help-guix@gnu.org; Mon, 16 Apr 2018 03:17:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f7yNl-0006Lw-28 for help-guix@gnu.org; Mon, 16 Apr 2018 03:17:00 -0400 Received: from mail-pg0-x241.google.com ([2607:f8b0:400e:c05::241]:43627) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f7yNk-0006Lm-Qp for help-guix@gnu.org; Mon, 16 Apr 2018 03:16:56 -0400 Received: by mail-pg0-x241.google.com with SMTP id f132so2262620pgc.10 for ; Mon, 16 Apr 2018 00:16:56 -0700 (PDT) In-reply-to: <87o9ijab7b.fsf@gmail.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Chris Marusich Cc: help-guix --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Chris Marusich writes: > If you or the > author of inxi are willing to learn more about this, I hope you did not think I was on the inxi's maintainer's side! :p I understand and agree with all your points. >> If anyone wants to chime in and try to convince the maintainer... > > Since you're the inxi user, I'll leave that to you. I hope I've helped > by giving enough information to clarify why GuixSD departs from the FHS, > and why inxi ought to let its users tell it where its dependencies live. Considering the maintainer's latest comments, I don't think he/she is open to discussion. It's too bad because I do not know any good alternative to inxi. Maybe it's time to solve this conky/i3status/inxi mess and roll out a Lisp-programmable/extensible monitor/reporter. What do you people think? >> Otherwise we will have to go ahead and patch inxi. > > That is always an option. We do it all the time, so it's nothing new. I'll go ahead then. =2D-=20 Pierre Neidhardt Nonsense. Space is blue and birds fly through it. -- Heisenberg --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlrUTeMACgkQm9z0l6S7 zH9l1gf/YDP3sZk/whrf6HygQPIKEhAzBfcw0d/r6xjey42GiiOX5VD9FzfqJeZ1 o2D2LxUidhy+SlHjR6I1cZiSrtV0bCgPp+94BbLUZmy0lOfNJKWYOhsx+PqO1CjU NVBTcnIt/10xc4LXAqBakTx+68EB6Es7sSx/+4rSm6TwJi9ZErSLq15rz3SaJTkE n2+oJBZApnGhzCv8R58i7GztWLQ4XssnOcCdRdRmbV0kWYnBU8Rs+xKY60B51KL8 cdb7I8AMrj5n6RYQH/R7oq47iUBma+DFAaPYxF4hEadEtXMJy1/M7rBMEda0Q0kE tPYyEO+SlnkVVYo7tit/6l859s6b5w== =xqEF -----END PGP SIGNATURE----- --=-=-=--