From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] python-pexpect: new package
Date: Wed, 9 Dec 2015 14:21:22 +0000 [thread overview]
Message-ID: <566838E2.4020401@imgtec.com> (raw)
In-Reply-To: <CAGm1_kuj=i5Z4uY92oM4-PH7kcnSK1PeYSHFQedUh3KGzdWNzA@mail.gmail.com>
Hello Yegor and Jan,
On 09/12/15 14:18, Yegor Yefremov wrote:
>> diff --git a/package/python-pexpect/Config.in b/package/python-pexpect/Config.in
>> new file mode 100644
>> index 0000000..a42aec7
>> --- /dev/null
>> +++ b/package/python-pexpect/Config.in
>> @@ -0,0 +1,10 @@
>> +config BR2_PACKAGE_PYTHON_PEXPECT
>> + bool "python-pexpect"
>> + depends on BR2_PACKAGE_PYTHON
>
> remove BR2_PACKAGE_PYTHON dependency
>
>> + select BR2_PACKAGE_PYTHON_PTYPROCESS
>> + help
>> + Pexpect is a pure Python module for spawning child applications; controlling them; and responding to
>> + expected patterns in their output. Pexpect works like Don Libes? Expect. Pexpect allows your script
>> + to spawn a child application and control it as if a human were typing commands.
>
> Lines must be max. 80 characters long
72.
Regards,
Vincent.
next prev parent reply other threads:[~2015-12-09 14:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 11:05 [Buildroot] [RFC PATCH] dpdk: new package Jan Viktorin
2015-10-30 17:17 ` Arnout Vandecappelle
2015-11-02 10:34 ` Jan Viktorin
2015-12-09 14:11 ` [Buildroot] [PATCH v2 0/3] " Jan Viktorin
2015-12-09 14:11 ` [Buildroot] [PATCH v2 1/3] python-ptyprocess: " Jan Viktorin
2015-12-09 14:16 ` Yegor Yefremov
2015-12-09 14:17 ` Vicente Olivert Riera
2015-12-09 14:11 ` [Buildroot] [PATCH v2 2/3] python-pexpect: " Jan Viktorin
2015-12-09 14:18 ` Yegor Yefremov
2015-12-09 14:21 ` Vicente Olivert Riera [this message]
2015-12-09 14:34 ` Jan Viktorin
2015-12-09 14:19 ` Vicente Olivert Riera
2015-12-09 14:11 ` [Buildroot] [PATCH v2 3/3] dpdk: " Jan Viktorin
2015-12-09 22:36 ` Thomas Petazzoni
2015-12-09 23:27 ` Jan Viktorin
2015-12-10 8:54 ` Thomas Petazzoni
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=566838E2.4020401@imgtec.com \
--to=vincent.riera@imgtec.com \
--cc=buildroot@busybox.net \
/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.
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.