All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>
Cc: sandeen@redhat.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/5] xfsprogs-4.17: mkfs config file enhancements
Date: Wed, 13 Jun 2018 23:23:09 -0500	[thread overview]
Message-ID: <c4ae2aaf-ee28-5c35-b3f5-ffe8a57d3c01@sandeen.net> (raw)
In-Reply-To: <20180614040628.GJ10363@dastard>

On 6/13/18 11:06 PM, Dave Chinner wrote:
> With this change, we'll have code to maintain it to ensure that the
> file gets updated properly, and it will probably take more time and
> effort to validate that the generated file is correct (and debug if
> it's not!) compared to the 30s it will take to hand edit the
> template file to change or add a new default...

Well, yeah.  /if/ we need a template, as well as text in a man page,
then this gets it down to editing 1 file instead of two, I guess.
But it really seems like we need to rethink these structures to get it
all tied together, not requiring 2 or 3 manual updates across several files.
It's bound to get out of sync.  I guess that can wait, but right now this
dispersal isn't good.

> I'm also not convinced we should ship a "default.template" file,
> either.  I'd much prefer we ship a real config file with all the
> options defined but commented out as a "start here template".

As the code stands today, if a 100% commented-out config file
exists, then mkfs will tell you that it's overriding built-in
defaults with the config file which contains ... nothing.
If we ship such a thing by default, that's what will happen by
default.

(Actually today it fails to parse and errors out but a patch
to fix that is on the list).

I guess we could behave as if "no config file" if a config file
contained no parseable tokens ... but that gets weird too.

Putting a blank config file in place to be parsed by default
is messy, so a .template approach seems reasonable to me, if we
need such a thing at all.

-Eric

  reply	other threads:[~2018-06-14  4:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 19:31 [PATCH 0/5] xfsprogs-4.17: mkfs config file enhancements Darrick J. Wong
2018-06-13 19:31 ` [PATCH 1/5] mkfs: move build-time defaults to a separate file Darrick J. Wong
2018-06-14  2:34   ` Eric Sandeen
2018-06-13 19:31 ` [PATCH 2/5] mkfs: move config file enums to config.h Darrick J. Wong
2018-06-14  2:51   ` Eric Sandeen
2018-06-14 16:24     ` Luis R. Rodriguez
2018-06-13 19:32 ` [PATCH 3/5] mkfs: hoist mkfs configfile dir string generation to build system Darrick J. Wong
2018-06-14  2:54   ` Eric Sandeen
2018-06-13 19:32 ` [PATCH 4/5] mkfs: emit config file from builtin defaults Darrick J. Wong
2018-06-14  3:05   ` Eric Sandeen
2018-06-13 19:32 ` [PATCH 5/5] mkfs: generate mkfs config file in man page Darrick J. Wong
2018-06-14  3:17   ` Eric Sandeen
2018-06-14  4:06 ` [PATCH 0/5] xfsprogs-4.17: mkfs config file enhancements Dave Chinner
2018-06-14  4:23   ` Eric Sandeen [this message]
2018-06-14  5:08     ` Dave Chinner
2018-06-14  6:29       ` Darrick J. Wong
2018-06-14 17:46         ` Luis R. Rodriguez
2018-06-14 17:59           ` Darrick J. Wong
2018-06-14 18:16             ` Luis R. Rodriguez
2018-06-14 18:35               ` Darrick J. Wong
2018-06-16  0:04                 ` Luis R. Rodriguez
2018-06-14 19:05             ` Eric Sandeen
2018-06-14 22:22               ` Dave Chinner
2018-06-14 23:33         ` Dave Chinner
2018-06-14 23:38           ` Eric Sandeen
2018-06-14 14:31       ` Eric Sandeen

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=c4ae2aaf-ee28-5c35-b3f5-ffe8a57d3c01@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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.