This is just a post to document some differences in webconf.lrp,
depending on where it comes from.
The short version is: If you use Bering-uClibc, use the webconf.lrp
included with Bering-uClibc. (e.g. you don't need to do anything, and
can ignore the rest of this message.)
In the cvs tree, leaf/devel/nangel/webconf/lrp/webconf.lrp is the
version that one gets if someone follows the twisty maze of web links to
download webconf.lrp "on its own."
This version contains
var/lib/lrpkg/webconf.exclude.list; this file excludes:
etc/webconf/*
var/webconf/*
The Bering-uClibc team has decided that those directories should be
owned by the mhttp(s) package, due to other file ownership issues.
This means a webconf.lrp built with buildtool.pl for a Bering-uClibc
will (correctly) *not* contain webconf.exclude.list. However, removing
the exclude.list from the binary .lrp file referenced above may break
backups on "classic" bering.
After a discussion with KP Kirchdoerfer, the binary webconf.lrp in
leaf/devel/nangel/webconf/lrp/webconf.lrp will continue to have the
webconf.exclude.list. The offical source code for all versions will
continue to be leaf/src/config/webconf.
In the past, whenever leaf/src/config/webconf changes, I committed a
webconf-[date].tar.gz in the Bering-uClibc source tree, and updated
buildtool.* to point to the new webconf source tarball. I will continue
to do so, until told otherwise by the Bering-uClibc team.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
