Hi Mats Mats Erik Andersson schrieb: ..
> > My proposal is to split the old package according to compiled > content and interpreted content, mainly because I find it somewhat > dishonest that I, as of recent times, have been made effective > maintainer of the scripted(!) part of Webconf and thereby will > import haserl and pwcrypt as old compiled executables, > since I have no access to any part of the cvs-tree outside > of Webconf. I personally prefer to see haserl and pwcrypt > being recompiled on the same machine as major parts of the > other executables contained in a Bering-uClibc release, > and not in the complete isolation that my own computers > constitute. It is a matter of compiler coherence and reliability. > But then, as long as the maintainers are content with > haserl and pwcrypt being carved out of stone for eternity > without any need for recompilation, I could certainly let > them stay inside webconf.lrp, and later delegate the rebuild > to a senior collaborator. I accept it, but I find the > subject worthy of everyones attention. > I understand your concerns. My understanding of a source repository is that in case of a new distribution everything gets recompiled from scratch so it does not depend on the setup of some developers workstation, but on the setup of a central compile and build system. Back in the Bering 1.2 times I ported haserl and pwcrypt back to glibc, as Nathan did not want to maintain it on that release. I was convinced as you are now, that the binaries should be kept separately from the web conten part. I placed the two executables in a .lwp package which was then placed in the LWP variable to be installed automagically when webconf was launched. 0.02 cheers Erich ------------------------------------------------------------------------- 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
