Re: Nightly CVS tarballs

SY> My motivation for this came about because I know of at least SY> one person whose firewall prevents them from using CVS. So in The firewall also prevents use of ssh? It would certainly be possible to make an anonymous retrieval only alias in Martin's auth files. We'd have to think about the security implications of that, but if the person would ask to formally recognized[1] as an XEmacs developer, or you're willing to personally vouch for them, it's probably doable. If they don't care that much, why should we care enough to go to this kind of trouble? It does have implications for our workload, over and above the setup of the cron job and the disk space. SY> that scenario whether or not the package will build is SY> probably not so important. Ask the person. SJT> - a 21.5 nightly tarball SJT> You will almost surely regularly get checkouts in the middle of a SJT> commit; XEmacs development is 24 hours a day. But commits aren't SJT> atomic. Is it worth it? SY> Development isn't that fast and furious is it? You're talking about doing this every day; the odds of a clean update on any given day are very good; the odds taken over a week are much worse. The odds over a month are bad. Anyway, when it is, it is. Right now is a lull; summers always are. Also, once I get out from under the start-of-term, I hope to do some recruiting.... SY> Granted there's a chance of getting a checkout in the middle SY> of someone else's commit, but the same can be said for SY> developers who use CVS anyway. CVS users can recheckout immediately and probably get a clean update. SJT> - perhaps individual package nightly tarballs SJT> This makes sense; people typically don't build their own SJT> packages, but download them with pui. This would free you SJT> from explicitly making "pre-releases," all you7d have to do SJT> is announce them. I think that's a good idea. SY> I get the impression you're thinking about this as another way SY> for users to get XEmacs or packages. Yes. Even if not your intention, it is that. That scares me. SY> That's not what I was thinking. I know; you don't field those bug reports. I do. ;-) Cf the guy who's been reporting 21.2.46 bugs. SY> It's more a way for developers who don't have SY> access to CVS to get hold of bleeding edge code so they can SY> hack to their hearts' content. :-) The fact is that the bleeding edge code _isn't on the trunk anymore_. It's on branches. So your theoretical developer without CVS access is S.O.L. anyway. 21.5-latest-beta is going to be pretty close to up-to-date, and it's very likely to build. Footnotes: [1] You know, like any of the committers. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."