From: Ben Elliston <bje@redhat.com>
To: sid@sources.redhat.com
Subject: sections in configrun-sid
Date: Fri, 10 Aug 2001 00:27:00 -0000 [thread overview]
Message-ID: <15219.36057.453159.217729@walkabout.brisbane.redhat.com> (raw)
This Perl script emits chunks of configuration data to three ordered
sections (named "$first_section", etc). At the end of the script,
each section is emitted to the configuration file in order.
I am finding this arrangement to be too restrictive. Currently, I
need to have a "$fourth_section" that makes use of some component
instantiation done late in the third section.
Instead, I think the logic could be simplified by creating a number of
sections, corresponding to the usual arrangement of sid configuration
files:
$preamble_section
$load_section
$new_section
$set_section
$connect_section
$postamble_section
Comments?
Ben
next reply other threads:[~2001-08-10 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 0:27 Ben Elliston [this message]
2001-08-10 0:58 ` matthew green
[not found] <15219.36057.453159.217729.cygnus.project.sid@walkabout.brisbane.redhat.com>
2001-08-10 1:34 ` Frank Ch. Eigler
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=15219.36057.453159.217729@walkabout.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=sid@sources.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).