From: ng0 <ng0@we.make.ritual.n0.is>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: help with setenv of perl-curses
Date: Sat, 06 Aug 2016 13:31:51 +0000 [thread overview]
Message-ID: <8760regh14.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <20160724052518.GA4905@debian-netbook>
Hi,
Efraim Flashner <efraim@flashner.co.il> writes:
> On Sat, Jul 23, 2016 at 01:18:10PM +0000, ng0 wrote:
>> Possibly fixed with this patch. Things I have not addressed so
>> far and require input on: How to do this
>> "perl Makefile.PL PANELS MENUS FORMS" in the setup.
>> Successfully built does not mean functional in all cases, so I
>> will build the package I needed this for now and see if it
>> changed.
>
> Sometimes using makeflags works for adding arguments to the `make'
> command, other times I've gone and replaced the 'make phase with a
> custom make phase. I haven't looked at the perl build system to see if
> makeflags works.
Coming back to this, should I build this with all the options? I had no
time to work on this again, so if someone else wants to add these
functionalities, go ahead.
--
♥Ⓐ ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-08-06 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 1:23 help with setenv of perl-curses ng0
2016-06-15 9:19 ` Ricardo Wurmus
2016-07-23 13:18 ` ng0
2016-07-23 13:58 ` ng0
2016-07-24 5:25 ` Efraim Flashner
2016-08-06 13:31 ` ng0 [this message]
2016-08-19 13:23 ` [PATCH] gnu: Add perl-curses (need help) ng0
2016-08-19 13:36 ` [PATCH][v2] gnu: Add perl-curses ng0
2016-09-06 17:36 ` Efraim Flashner
2016-09-06 21:39 ` ng0
2016-09-07 6:09 ` Efraim Flashner
2016-07-25 8:18 ` help with setenv of perl-curses Vincent Legoll
2016-08-06 13:28 ` ng0
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=8760regh14.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=efraim@flashner.co.il \
--cc=guix-devel@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 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.