Hello folks,

I will the next few days commit a major overhaul of Webconf,
resulting in new versions of at least five webconf packages.
The most drastic change I implement is to render the web
pages for a fixed width in order to ensure a consistent
optical impression. Any objections should be expressed now!

Let me raise a possible issue with "webconf.lrp". Some time
ago KP informed me of an earlier decision of the developer
circle, saying that scripted services like my cgi-scripting are not
maintained inside the CVS-tree for Bering-uClibc, but instead
it is the externally manufactured lwp-packages and "webconf.lrp"
that do get committed into the official repository. In my present
work for the upcoming beta cycle I have observed that "webconf.lrf"
indeed does contain TWO compiled binaries:

   /usr/sbin/haserl
   /usr/sbin/pwcrypt

My naive thought is that these two ought to be moved into a
separate package to enhance the maintenance of their sources.
It is true that the outdated version of haserl used for Bering-uC
is halfway orphaned by the original upstreams developer Nathan
Angelakos, but in case Bering in the (very) long run considers
a migration to the Lua suporting newer Haserl edition, then it
is all the more important to keep the  sources of Haserl inside
our CVS-tree, instead of an external binary in "webconf.lrp".
This issue needs no immediate action, but I wanted to mention this.
Of course, considerations on a new kernel series and a later
library issue than presently used, both deserve higher priority,
but the state of haserl can be solved/improved in less than an hour,
should you decide to put it in a separate package.

Best regards

Mats Erik Andersson 

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

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

Reply via email to