On Fri, Jun 20, 2003, Bill Campbell wrote:
Bill,
> 1. Specify all configuration files that are essential to program
> operation ``%config(noreplace)'' (e.g. postfix's main.cf, samba's
> smb.conf, etc.) to avoid breaking production systems when doing
> updates.
I don't think there is a correct way. You may either fail with the old
or the new configuration. With the default %config the user configuration
is only modified when the default configuration changes, in that case
it is likely that the user configuration is broken.
What we need is some kind of sanity checking. For example, the rc file
could prevent a service from beeing started when there is a .rpmsave
configuration present.
> 2. In liew of implementing package-specific options in ~/.openpkg/build,
> use option names such as ``with_vim_x11'' instead of the more generic
> ``with_x11''.
The current version of the build tool supports package specific options,
i.e.: vim::with_x11.
> 3. Add options ``with_%{name}_doc'' to allow the builder to include
> documentation. One package that really wants to have documentation
> on-line is Samba when using ``swat'' since one of the primary reasons
> for using swat is easy access to the documentation when configurating
> obscure options.
Some packages do include documentation, some don't. The minimum we need
is some consistent packaging. Making documentation beyond a basic man-page
available by an option (%{name}::with_doc, see above) sounds like a good
idea.
Greetings,
--
,eM""=. a"-. Michael van Elst
dWWMWM" - :GM==; [EMAIL PROTECTED]
:WWMWMw=--. "W=' cable & wireless
9WWMm==-.
"-Wmw-" CABLE & WIRELESS
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
