From: Michal Marek <mmarek@suse.cz>
To: Andreas Mohr <andi@lisas.de>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Roman Zippel <zippel@linux-m68k.org>,
Waldo Bastian <bastian@kde.org>, Ryan Lortie <desrt@desrt.ca>,
Lennart Poettering <lennart@poettering.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Heads-up: Linux make menuconfig .config vs. XDG_CONFIG_HOME ~/.config/ clash - perhaps resolve it while 3.0 appears?
Date: Fri, 03 Jun 2011 10:25:46 +0200 [thread overview]
Message-ID: <4DE89A8A.8070405@suse.cz> (raw)
In-Reply-To: <20110602182431.GA26282@rhlx01.hs-esslingen.de>
On 2.6.2011 20:24, Andreas Mohr wrote:
> I just discovered a Linux kernel make menuconfig .config file
> accidentally situated in the home directory of a shell account
> [...]
> "$XDG_CONFIG_HOME defines the base directory relative to which user
> specific configuration files should be stored. If $XDG_CONFIG_HOME is
> either not set or empty, a default equal to $HOME/.config should be
> used."
PEBKAC :-). BTW, did you really run into such problem yourself, or is it
more a "what if"?
> It may thus be strongly advisable to rename the default name of the
> make menuconfig kernel .config file (perhaps .config_lx / .config_linux ?)
> to completely sidestep such a (mostly user-triggered)
> problematic clash in future.
No. The name ".config" is documented in the linux source as well as so
many howtos and books, that we should not change it just for the fun of
it. Arguably, a non-dot filename might have been a better choice, but
".config" has been chosen, so we have to live with it.
> And (I cannot help but think of this) now that lx 3.0 is in -rc
> this might still be an especially appropriate moment to do it ;)
Linus made it clear that 3.0 is just a change in versioning, not an
excuse for doing incompatible changes. (Incompatible changes can
possibly happen in any release, but they need to be justified and need
to be ready *before* -rc1.)
Michal
next prev parent reply other threads:[~2011-06-03 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 18:24 Heads-up: Linux make menuconfig .config vs. XDG_CONFIG_HOME ~/.config/ clash - perhaps resolve it while 3.0 appears? Andreas Mohr
2011-06-03 8:25 ` Michal Marek [this message]
2011-06-03 13:17 ` Andreas Mohr
2011-06-03 14:38 ` Nick Bowler
2011-06-03 16:44 ` Arnaud Lacombe
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=4DE89A8A.8070405@suse.cz \
--to=mmarek@suse.cz \
--cc=andi@lisas.de \
--cc=bastian@kde.org \
--cc=desrt@desrt.ca \
--cc=lennart@poettering.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.