Your message dated Wed, 22 Jun 2011 09:36:43 +0100
with message-id <[email protected]>
and subject line Re: Bug#630258: [PATCH] multistrap: Document the "include"
setting.
has caused the Debian Bug report #630258,
regarding [PATCH] multistrap: Document the "include" setting.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
630258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630258
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: multistrap
Version: 2.1.14, 2.1.14+svn8003
Tags: patch
Would also need a couple of words about the possibility to use several
values here. A quick test shows that the first ones seems to take
precedence over further ones, but it is not quite clear at first code read
if that is intended.
---
pod/multistrap | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/pod/multistrap b/pod/multistrap
index ea340a7..b9fb354 100644
--- a/pod/multistrap
+++ b/pod/multistrap
@@ -133,6 +133,9 @@ configuration files should be C<bootstrap> instead.
=head1 General settings:
+'include' specifies a config file whose settings will be used, and
+possibly overridden by the ones in the current file.
+
'arch' can be overridden on the command line using the C<--arch> option.
'directory' specifies the top level directory where the bootstrap
@@ -368,8 +371,9 @@ See also
=head1 Cascading configuration
To support multiple variants of a basic (common) configuration,
-C<multistrap> allows configuration files to include other (more general)
-configuration files. i.e. the most detailed / specific configuration
+C<multistrap> allows configuration files to include other (more
+general) configuration files, using the 'include' settings of the
+"General" section. i.e. the most detailed / specific configuration
file is specified on the command line and that file includes another
file which is shared by other configurations.
--- End Message ---
--- Begin Message ---
On Wed, 22 Jun 2011 01:20:04 +0200
Yann Dirson <[email protected]> wrote:
Don't play around with bug reports. This bug has been closed.
> > Patch is not acceptable as it demonstrates misunderstandings of the
> > existing documentation and the manpage is quite long enough as it is.
> > There is plenty more documentation on the website and the wiki.
>
> Ok I admit that I have misunderstood, but this answer is not that useful.
>
> So (appart from *not* being documented as a keyword, "include" here
> just does not have the usual semantics we see in "include" mechanisms
> - and as such, without proper docs, it is sure to confuse users.
>
> So the question is, how best can we describe the behaviour ?
Expand the Wiki content, there's no place for this in the manpage which
is already too long. Suitable content from the wiki can then be
included into the website.
--
Neil Williams
=============
http://www.linux.codehelp.co.uk/
pgpUYmxllKLQH.pgp
Description: PGP signature
--- End Message ---
