mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kconfig-frontends-3.4.0-0 released
Date: Wed, 23 May 2012 00:11:28 +0200	[thread overview]
Message-ID: <201205230011.29257.yann.morin.1998@free.fr> (raw)
In-Reply-To: <20120522211941.GA30024@home.goodmis.org>

Steven, All,

On Tuesday 22 May 2012 23:19:41 Steven Rostedt wrote:
> >   - some side utilities have been added from the Linux kernel tree:
> >     - kconfig-diff      show differences between two .config files
> 
> I'm curious, how is this different than scripts/diffconfig ?

It's exactly the same.

The kconfig-frontends package is created by extracting the needed files from
the linux kernel. So, kconfig-diff is exactly scripts/diffconfig. Also, it's
what the line just above says: "added _from_ the Linux kernel tree" ;-)

But the kconfig toolss in the linux tree are not using a common naming
scheme. For example we have:
    scripts/config
    scripts/diffconfig
    scripts/kconfig/merge_config.sh
    scripts/kconfig/kxgettext
    scripts/kconfig/conf
    scripts/kconfig/mconf

So, kconfig-frontends tries to use a meaningful naming scheme for all the
programs it installs. Some are renamed, and they all get prefixed by default
with 'kconfig-' (although that can be overriden at ./configure time with
--program-prefix=...).

In the package, the file scripts/kernel2kfrontends.list has the
correspondence for what comes from the linux tree, and how it's named in
the kconfig-frontends tree. For example, we have:
    scripts/config                      -->  utils/tweak
    scripts/diffconfig                  -->  utils/diff
    scripts/kconfig/merge_config.sh     -->  utils/merge
    scripts/kconfig/kxgettext.c         -->  utils/gettext.c

The script scripts/ksync.sh (in kconfig-frontends) uses that file to
automatically sync from a linux tree.

There is virtually zero code written in the package (except for a few patches
required for the packaging), so the behavior is exactly the same as if using
the corresponding kconfig tools from the kernel.

Please note, however, that this is only the second release of
kconfig-frontends, and that things can still be improved upon! ;-)

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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2012-05-22 22:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 20:21 Yann E. MORIN
2012-05-22 21:19 ` Steven Rostedt
2012-05-22 22:11   ` Yann E. MORIN [this message]
2012-05-22 22:21     ` Steven Rostedt

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=201205230011.29257.yann.morin.1998@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®