Re: eval-when, eval-when-compile

* "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp&gt; writes: SJT> I will say, as an aside, that the last few months of hacking SJT> on the package build process have been a massive step SJT> backward. :-( I have this dream of autoconf'ing the package build process. :-) mb> Paging Steve Youngs... mb> I have certain release criteria for 21.2 beta, like successful mb> C++ compiles and clean `make check's. I would hope package mb> releases would have similar release critieria. Yes I do follow similar procedures for package releases. Stephen> I don't think this is a Steve Youngs problem, unless he wants to claim Stephen> it. If it's package related, I don't mind taking it on. Stephen> missing statement of purpose. Is there a "statement of purpose" for the core distribution? Where's it at? Perhaps I can knock something up for packages. Stephen> We don't have a review procedure for Stephen> changes to the package infrastructure. I don't know whether the Stephen> package system should be treated like the stable branch, with a single Stephen> gatekeeper, but we should consider that (if we can find somebody who Stephen> is willing to own the Makefiles, package-compile.el, etc). I I think taking a leaf out of Vin's book would be a good idea for the packages. I'll gladly adopt the Makefiles etc. Stephen> We need a Mule policy What are your thoughts on this, Stephen? -- |---<Regards, Steve Youngs>-----------[GnuPG KeyID: 59E4C4B2]---| | XEmacs - It's not just an editor... | | It's a way of life. | |----------------------------------<mailto:youngs＠xemacs.org>---|