From: Geert Bevin <gbevin@theleaf.be>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Package configuration
Date: 19 Nov 2001 11:42:34 +0100 [thread overview]
Message-ID: <1006166554.23698.2.camel@willow> (raw)
Hello,
I've been playing a bit with portage and try to create a stable and easy
to use postgres package. Doing this I noticed something missing in
portage (maybe I'm just overlooking it, and then all what follows is
obsolete ;-) ).
Typically a package has a configuration phase which occurs after merging
it into the system. This configuration is optional, but could be done
both for binary as source packages. For postgres this is for example the
initialization and installation of an empty database instance. Rocklinux
solves this in a very simple and easy to use manner. It contains an
/etc/setup.d/ directory with simple shell scripts prepended by numbers
in their names (eg. 00-general, 10-gpm, 20-network, 50-sshd, 70-pgsql,
...) It uses these numbers to execute all configs sequentially when a
binary clean install is done from cd. This makes the initial
configuration process modular and very manageable.
When installing a package, emerge could monitor /etc/setup.d/ in a
similar way as it monitors /etc and report whether a new config file is
present and that it can be executed to configure the package that just
was merged.
I hope I explained clearly enough. Tell me what you think of it.
Best regards,
--
Geert Bevin
the Leaf sprl/bvba
"Use what you need" Pierre Theunisstraat 1/47
http://www.theleaf.be 1030 Brussels
gbevin@theleaf.be Tel & Fax +32 2 241 19 98
next reply other threads:[~2001-11-19 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-19 10:42 Geert Bevin [this message]
2001-11-19 11:09 ` [gentoo-dev] Package configuration Mikael Hallendal
2001-11-19 15:05 ` Chris Houser
2001-11-19 15:50 ` Geert Bevin
2001-11-19 18:26 ` Martin Schlemmer
2001-11-21 18:20 ` Geert Bevin
2001-12-22 16:21 ` Daniel Robbins
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=1006166554.23698.2.camel@willow \
--to=gbevin@theleaf.be \
--cc=gentoo-dev@gentoo.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