From: "André Erdmann" <dywi@mailerd.de>
To: gentoo-soc <gentoo-soc@lists.gentoo.org>
Cc: Rafael Martins <rafaelmartins@gentoo.org>
Subject: [gentoo-soc] kernelconfig - progress report #2
Date: Fri, 3 Jun 2016 23:42:16 +0200 [thread overview]
Message-ID: <CAGrucu15tB+Venhsxx13W7SQcd7-R2BZ4pn7YGG2LCtG2Fyffw@mail.gmail.com> (raw)
Hi everyone,
== Brief summary of this project ==
kernelconfig is about generating kernel configuration files,
using various sources such as curated defconfigs, detected hardware,
installed packages and user input.
The project's code can be found at [0].
== This week's progress ==
A Python-level kernelconfig interface for modifying kernel configurations.
Basically, it wraps a config object, offers modify-option
(builtin, module, disable, set to value, ...) methods that write to a
"decision" buffer which gets checked for direct conflicts, and a commit()
method that merges the decisions with the original config.
It is also responsible for resolving a working configuration
(dependencies!), which I'm currently working on.
== Plans for the next week ==
Work on resolving dependencies,
so that a working configuration can be created.
[0] https://github.com/dywisor/kernelconfig
Regards,
André E.
reply other threads:[~2016-06-03 21:42 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=CAGrucu15tB+Venhsxx13W7SQcd7-R2BZ4pn7YGG2LCtG2Fyffw@mail.gmail.com \
--to=dywi@mailerd.de \
--cc=gentoo-soc@lists.gentoo.org \
--cc=rafaelmartins@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