From: "André Aparício" <aparicio99@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] libbash - Progress report #4
Date: Tue, 19 Jun 2012 02:39:57 +0100 [thread overview]
Message-ID: <20120619023957.546da074@null> (raw)
Hi again,
=== Progress of previous week ===
- Still fixing some things in the commits from the previous sprint,
including rewriting the read builtin to be less "C-like"
- Improve the declare builtin with multiple variables, value
assignment, and the "-i", "-a" and "-g" options.
- Use script content as script name, to make it easy to identify errors
- Finish some touches on redirection, adapting the tests to a little
change in the grammar, and adding support for "here strings" (<<<).
With this we can finish generating metadata without blocking in the
read builtin waiting for input.
=== Plan for this week ===
- Fix commits from previous week
- Improve command arguments parsing
- Upgrade our instruo implementation to work with paludis 0.74.1
- Fix configure to fail when paludis is not installed
https://github.com/Aparicio99/libbash
Best regards,
André Aparício
reply other threads:[~2012-06-19 3:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120619023957.546da074@null \
--to=aparicio99@gmail.com \
--cc=gentoo-soc@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox