Hi Folks testing some of the webconf enabled tools I found that some paths have changed, particularly traceroute, which used to be a package on it's own, now it appears to be a busybox applet. It used to be at /usr/sbin, now it is at /usr/bin. Of course this is a challenge for the webconf package.
I am not sure if a construct of the form TRACEROUTE=`which traceroute` $TRACEROUTE $address is the best solution for this kind of a problem. Changes like this may happen any time in any package and are difficult to detect without proper regression testing. I always was (and I still am) in favour of including the relevant webconf files in the corresponding .lrp packages. This leverages the risk of such glitches, as the developer, even if he could not care less about the GUI, will kow best about the changes he made to the underlying software. I would like you to reconsider the decision taken on this issue a few months ago. I intend to provide this to openswan in the form of generating an additional package which can be loaded at the user's discretion, something like either ipsec.lrp, which is the standard package we are used to. ipsec-wc.lrp, which is the standard package with included web gui. webconf-1.2 shows how this can be crufted together without pain. I am of the opinion, the .lwp files should be gotten rid of (Scipio would have loved this construct :-) ) my 0.02 € Erich ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
