From: Denis Romanchuk <den4ikkss@gmail.com>
To: gentoo-soc@lists.gentoo.org, radhermit@gentoo.org
Subject: [gentoo-soc] Re: libebuild - weekly report #8
Date: Mon, 18 Jul 2016 06:50:01 +0300 [thread overview]
Message-ID: <63863448.Y69znmlREn@yo> (raw)
In-Reply-To: <14396076.rpDzvke5XW@yo>
Hello,
My eight week progress:
This week I've mostly spent to get more familiar with some of the pkgcore
subsystems implementation and examine following tasks.
Plan for next week:
Work on restrictions and other pkgcore/libebuild improvements,
Take out conditional restrictions into separate restrictions
module(conditional) and come up with new design(remove recursive use
conditional evaluation in particular) which will help to reduce memory
consumption in case of a lot of conditional use dependencies appears and also
should simplify other code paths.
Libebuild repo https://github.com/den4ix/libebuild
Libebuild blog https://blogs.gentoo.org/gsoc2016-libebuild/
--
Denis Romanchuk
Kiev, Ukraine
Email: den4ikkss@gmail.com
next prev parent reply other threads:[~2016-07-18 3:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 20:55 [gentoo-soc] libebuild - weekly report #1 Denis Romanchuk
[not found] ` <20160529210437.GA15760@tarragon.radhermit.com>
[not found] ` <3632285.5djuBY1Kdt@yo>
2016-06-06 0:37 ` [gentoo-soc] libebuild - weekly report #2 Denis Romanchuk
2016-06-13 3:42 ` [gentoo-soc] Re: libebuild - weekly report #3 Denis Romanchuk
2016-06-20 4:36 ` [gentoo-soc] Re: libebuild - weekly report #4 Denis Romanchuk
2016-06-26 23:14 ` [gentoo-soc] Re: libebuild - weekly report #5 Denis Romanchuk
2016-07-11 2:01 ` [gentoo-soc] Re: libebuild - weekly report #7 Denis Romanchuk
2016-07-18 3:50 ` Denis Romanchuk [this message]
2016-07-31 22:58 ` [gentoo-soc] Re: libebuild - weekly report #10 Denis Romanchuk
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=63863448.Y69znmlREn@yo \
--to=den4ikkss@gmail.com \
--cc=gentoo-soc@lists.gentoo.org \
--cc=radhermit@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