Hello there,

I have been thinking through the contents of the
Bering package "webconf.lrp", since it contains
two compiled pieces of code, some images, and
for the rest only script code and one css-file.

My conclusion is to advocate a split into two
separate packages. The first would contain the
two compiled executables (haserl and pwcrypt):

Initially haserl.lrp with contents
          ==========

---- list of content for haserl.lrp ----
usr/bin/pwcrypt
usr/bin/haserl
var/lib/lrpkg/haserl.conf
var/lib/lrpkg/haserl.help
var/lib/lrpkg/haserl.version
var/lib/lrpkg/haserl.local
---- end of list ----


Thus a sensible versioning is restored
for the C source code.

Next, the Webconf infrastructure would go 
into a revised package webconf.lrp containing
                       ===========

---- list of content for webconf.lrp ----
etc/webconf/webconf.conf
etc/webconf/webconf.webconf
etc/init.d/webconf
var/webconf/www/pix/dg.png
var/webconf/www/pix/dr.png
var/webconf/www/pix/dy.png
var/webconf/www/pix/lg.png
var/webconf/www/pix/logo1.gif
var/webconf/www/pix/logo1.jpg
var/webconf/www/pix/logo2.gif
var/webconf/www/pix/lr.png
var/webconf/www/pix/ly.png
var/webconf/www/blurb.basic
var/webconf/www/connection-info.cgi
var/webconf/www/general-info.cgi
var/webconf/www/index.cgi
var/webconf/www/logfiles.cgi
var/webconf/www/lrcfg.back.cgi
var/webconf/www/wc-passwd.cgi
var/webconf/www/webconf.css
var/webconf/www/.htpasswd
var/webconf/lib/footer.sh
var/webconf/lib/menubuilder.sh
var/webconf/lib/preamble.sh
var/webconf/lib/svcstat.sh
var/webconf/lib/validator.sh
var/webconf/lib/widgets.sh
var/webconf/lib/filter/daemon.log.show.request-ack
var/webconf/lib/filter/debug.only.REQUEST
var/webconf/lib/filter/messages.non-MARK
var/lib/lrpkg/webconf.conf
var/lib/lrpkg/webconf.help
var/lib/lrpkg/webconf.version
var/lib/lrpkg/webconf.local
---- end of list ----

In comparison to the presently used "webconf.lrp" content,
only the two executables are to be moved out, and they
must then be enhanced with the lrpkg informational files
in the (revived) package "haserl.lrp". For the end user
there would be two packages needed to implement the webconf
funtionality, and also a package dependency 

  "webconf.lrp depends on haserl.lrp"

which must be made clear in the user documentation.


Discussion is welcome!

Best regards

Mats Erik A

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to