From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: inxi and inxi-full Date: Fri, 13 Apr 2018 11:54:45 +0530 Message-ID: <87y3hroc7m.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> 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]:33108) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f6s8k-0001Rs-O6 for help-guix@gnu.org; Fri, 13 Apr 2018 02:24:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f6s8h-0004yq-Kn for help-guix@gnu.org; Fri, 13 Apr 2018 02:24:54 -0400 Received: from mail-it0-x22e.google.com ([2607:f8b0:4001:c0b::22e]:51771) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f6s8h-0004yZ-Ee for help-guix@gnu.org; Fri, 13 Apr 2018 02:24:51 -0400 Received: by mail-it0-x22e.google.com with SMTP id b5-v6so1923135itj.1 for ; Thu, 12 Apr 2018 23:24:51 -0700 (PDT) In-reply-to: <87in8vws4e.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 Chris Marusich writes: >> Why would we need to wrap the program? With the above fix, then we are >> all good, aren't we? > > If we do what you suggest, then all the "system" invocations should work > fine, but we'll still need to wrap the script so that it finds the > required Perl libraries. For an example of how to do that, see the > definition of perl-image-exiftool in (gnu packages photo). OK. > I'm actually a little surprised that the perl-build-system doesn't take > care of this automatically for us; we might want to fix that. If you're > feeling ambitious, maybe you could submit a patch to add a phase to the > perl-build-system's %standard-phases that finds executable perl scripts > and wraps them automatically. Sadly, I know next to nothing about Perl. I'd rather leave this to someone with some Perl knowledge. > You probably know about what inxi users expect than I do, since I've > never used inxi, so ultimately I'll defer to your judgment here. Yes, inxi makes it very clear that it can be composed dynamically. This is precisely how it's used on most major distributions I think. https://aur.archlinux.org/packages/inxi/ Cf. the documentation and the `inxi --recommends` output. -- Pierre Neidhardt Mirrors should reflect a little before throwing back images. -- Jean Cocteau --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlrQTS4ACgkQm9z0l6S7 zH//Cwf/b0Un7GRy/H+Im2pikB9y3l3L2MKGUFkjjXhgjD0Hq8QCN0qa389ot66q uT0NyVfldb+jBuyHZGPZ/LVIrcl4ljEDbEjTWI/jZD1bLpAglO6bNPudcX6ksCeF 0ZiulkmO5fPAvGl+L909eR9kRDbFnEyoPDpS9xnS2ehwQFG+slh2+ZHC/tHZOBYu c0ojwl21q8qwauhJ2YczkEt1wq8Vo8AAlAMO98Wi7OaMdiQcx066riEafQCLt6Se TiXeg5mADUPsaJ1zwPd5KJtO9vTeUMOut4UJKwMfECKDV8mt6lfm88MRzOSse/Zq 3z+Si1T46U8mFDVBkUXGyfU9OtvbGA== =YtKi -----END PGP SIGNATURE----- --=-=-=--