libbash weekly report #11

Sorry for the delay this time because I was in Beijing in the last weekend. Finally I can get down to write the report.

Now 8414 ebuilds can be handled. The number is increasing again and it’s not that hard to make progress this time because we have fixed the big issues in the parser grammar. However, running instruo is not that fast any more. It is because we can parse more eclasses so there are more things to handle.

I did more than expected in the last week. Here is the list of what I have done in the last week:

  • Fix code so that our instruo won’t crash anymore(turns out to be a problem related to thread-safety)
  • Get libtool.eclass fully parsed
  • Get perl-module.eclass fully parsed
  • Get distutils.eclass fully parsed
  • Get java-utils-2.eclass fully parsed
  • Get kde4-base.eclass fully parsed
  • Get python.eclass parsed with one exception: double quoted arithmetic expansion

The above eclasses included all the tasks for grammar improvements that I mentioned in the last weekly report.

This week I will:

  • Improve our build system to install something useful
  • Improve our ebuild so that the library can be installed and used properly
  • Review all the documentation
  • Review all the code
  1. #1 by Pavel on August 3, 2011 - 7:57 pm

    Great to see your progress! Do you have any idea when libbash could actually hit users?

    • #2 by qiaomuf on August 3, 2011 - 8:17 pm

      I think users can play with it at the end of GSoC 2011 if their usage is not quite complex. I’ll update the documentation and ebuild to make sure it’s usable at that time. To know what is not quite complex, there are scripts that cover what libbash supports:;a=tree;f=scripts;hb=HEAD

      However, it will take some time to make libbash do some complicated tasks, for example, being able to parse all the eclasses. Although many features are supported now, it’s tricky to parse all the eclasses because you can almost see every syntax covered by bash manual and many complicated cases in the eclasses.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: