From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from smtp11.smtpout.orange.fr ([80.12.242.133] helo=smtp.smtpout.orange.fr) by merlin.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux)) id 1SA7N1-0003ke-KX for barebox@lists.infradead.org; Tue, 20 Mar 2012 22:17:36 +0000 From: "Yann E. MORIN" Date: Tue, 20 Mar 2012 23:17:31 +0100 MIME-Version: 1.0 Message-Id: <201203202317.31289.yann.morin.1998@free.fr> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: kconfig-frontends: a packaging of the kconfig language To: barebox@lists.infradead.org Hello All! I am glad to announce the kconfig-frontends' first release ever! kconfig-frontends-3.3.0-0 was released today, right after the corresponding Linux kernel was released! Go download it there: http://ymorin.is-a-geek.org/download/kconfig-frontends/kconfig-frontends-3.3.0-0.tar.xz The kconfig-frontends (temporary) home is at: http://ymorin.is-a-geek.org/projects/kconfig-frontends The kconfig-frontends project aims at centralising the effort of keeping an up-to-date, out-of-tree, packaging of the kconfig infrastructure, ready for use by third-party projects. The kconfig-frontends package provides the kconfig parser, as well as all the frontends, packaged using the traditional autotools, so the kconfig infrastructure is easy to deploy, either locally or system-wide. What you get with kconfig-frontends: - all five frontends: conf, mconf, nconf, gconf and qconf - a shared and/or static library and the headers for the parser, so any one can build their own frontend - the standard "./configure && make && make install" dance - an easy way to sync from a newer kernel - a bit of documentation kconfig-frontends is not meant to replace the in-tree Linux kconfig (at least in the foreseeable future!), but really targets third-party projects that want an easy path to following the evolution of kconfig, without the burden to manually synchronise occasionally. The plans for the future are: - release with every Linux kernel dot-0 release - release with every Linux kernel dot-release if there are kconfig fixes - release to fix blocking issues with the packaging - find a proper home (mid-term) - migrate the repository to git (short-term) - improve the documentation! Any comment, any feedback is welcome! ;-) Note: kconfig-frontends is only about the kconfig language: the parser and the frontends; it's not about kbuild, the Linux kernel build infrastructure. I am sending this news to all projects I know of, that are using the kconfig language, or a derivative, as their configuration infrastructure, in the hope they find this news interesting. This is a one-off email, and no further announcement will be sent to your projects mailing-lists unless you express interest in future such announcements. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------' _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox