public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Package configuration
Date: Mon, 19 Nov 2001 20:26:34 +0200	[thread overview]
Message-ID: <1006194396.28665.11.camel@nosferatu.lan> (raw)
In-Reply-To: <1006185046.339.0.camel@willow>

[-- Attachment #1: Type: text/plain, Size: 2081 bytes --]

On Mon, 2001-11-19 at 17:50, Geert Bevin wrote:
> > Usually, portage addresses this by providing good defaults and then
> > documentation for less standard configuration.  If you need something to
> > be executed (non-optionally) after merge, you can define a
> > pkg_postinst() function in your ebuild.  I think this addresses a large
> > percentage of the cases without adding a more complex mechanism.
> 
> Problem is this example situation. I install postgres which creates the
> default database by default. Then one day I want to upgrade and again a
> default database is created and it overwrites the existing one ....
> major catastrophy ! Having a setup script available and notifying the
> user of its existance makes it easy to install a default setup without
> having to wade through the manuals of all the software before being able
> to use it and protects an unwary user from accidentally erasing or
> overwriting existing data files.
> 

What about the setup script (or pkg_postinst() ) checking if the default
database exist before creating it ?

> > Some sort of post-install user interaction has been discussed, with
> > everything from an interactive config GUI to listing recommended
> > documentation.  This may be written eventually, but the set of possible
> > solutions is large, diverse, and heavily dependant on personal taste,
> > all of which tend to slow down the actual writing of code.
> 
> Imho, starting with basic bash scripts is a good approach. When text ui
> and gui become available additional support for those can be added
> later.
> 
> 
> -- 
> 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
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop Team Developer
Cape Town, South Africa


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-11-19 18:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-19 10:42 [gentoo-dev] Package configuration Geert Bevin
2001-11-19 11:09 ` Mikael Hallendal
2001-11-19 15:05 ` Chris Houser
2001-11-19 15:50   ` Geert Bevin
2001-11-19 18:26     ` Martin Schlemmer [this message]
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=1006194396.28665.11.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --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