<div>I like the availability of a mzscheme-only package - it allows you to deploy a minimal system in a production environment.</div> <div> </div> <div>Thanks,</div> <div>yc</div> <div> </div> <div class="gmail_quote">On Wed, Nov 11, 2009 at 8:57 AM, Jay McCarthy <span dir="ltr"><<a href="mailto:jay.mccarthy@gmail.com">jay.mccarthy@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I personally don't see any value in leaving out the docs or DrScheme.<br>Everything is so small anyways and hard drive space is cheap... I<br> don't get the use case.<br><font color="#888888"><br>Jay<br></font> <div> <div></div> <div class="h5"><br>On Wed, Nov 11, 2009 at 8:25 AM, Matthias Felleisen<br><<a href="mailto:matthias@ccs.neu.edu">matthias@ccs.neu.edu</a>> wrote:<br>><br>> Thanks for the responses. The responses propose three natural things:<br> ><br>> 1. We need the nightly builds.<br>><br>> 2. Eli's component rules must be turned into something that people can read<br>> up on.<br>><br>> 3. The email about rule violations should not go to Eli but to plt-dev.<br> > (It's all implemented, no need to shift it anywhere.)<br>><br>> ;; ---<br>><br>> There were no comments on component-oriented distribution.<br>><br>> -- Matthias<br>><br>><br>><br>><br> ><br>><br>><br>> On Nov 10, 2009, at 12:20 PM, Matthias Felleisen wrote:<br>><br>>><br>>> Ladies and gentlemen,<br>>><br>>> Eli spent my first hour++ in my office this morning pointing our serious<br> >> flaws in our world. Here are two important points, and I am putting them up<br>>> for discussion here with a request for sensible comments:<br>>><br>>> 1. In some way we have been conducting a social experiment for the past 10<br> >> days or so. As you all know, Eli spent a considerable time creating the<br>>> nightly build framework when he first arrived here. From the nightly build,<br>>> Eli's software also creates a nightly set of deliveries and puts them up on<br> >> the web somewhere. What you ma not realize is that the nightly builds have<br>>> been broken for some 10 days due to the check-in of a module that breaks the<br>>> component delivery mechanism.<br>>><br> >> Nobody complained, so our conclusion was that nobody noticed. Our second<br>>> corollary was that perhaps we only have a camel-back distribution of users:<br>>> those who use svn and build from svn and those that use only the releases.<br> >> (As Eli walked out of my office, I switched to my email and the first<br>>> message contained a complaint about the missing nightly deliveries. This<br>>> means we know of one user of the deliveries.)<br> >><br>>> 2. Which brings me to the topic of "delivery by component." Apparently<br>>> few, if anyone here, is aware of Eli's carefully arrange delivery layers:<br>>><br>>> -- smallest: plain mzscheme, no mred, no docs<br> >> -- mid size: mred, drscheme, no docs<br>>> -- largest: everything<br>>><br>>> Eli tells me that there are numerous people who use 'smallest'; I don't<br>>> know about mid.<br> >><br>>> He (and I and I know Robby) have for a long time envisioned a delivery<br>>> system that starts with a core package and then asks (possibly via some gui)<br>>> what other packages should be installed, e.g., the 'mred' layer or the<br> >> server. The three-tier delivery system is a first step toward this<br>>> component-oriented delivery.<br>>><br>>> Eli has carefully maintained a dependency graph and list (that takes some<br>>> 11megs) among the various files (8 platforms, 3 tiers, everything spelled<br> >> out). Since people aren't really aware of this system, they easily and<br>>> apparently relatively often break the non-cyclic dependencies. (I am guilty<br>>> of doing this myself when I wrote the first docs that depended on<br> >> slideshow.)<br>>><br>>> In my opinion, we have two options:<br>>><br>>> -- drop the dependency system and just deliver one large package<br>>> -- enforce the dependencies. If you break them, you get a message.<br> >> If you don't clean them up in N hours, the file is removed.<br>>><br>>> ;; ---<br>>><br>>> As I said, sensible comments welcome. -- Matthias<br>>><br>>><br>>><br>>><br> >> _________________________________________________<br>>> For list-related administrative tasks:<br>>> <a href="http://list.cs.brown.edu/mailman/listinfo/plt-dev" target="_blank">http://list.cs.brown.edu/mailman/listinfo/plt-dev</a><br> ><br>> _________________________________________________<br>> For list-related administrative tasks:<br>> <a href="http://list.cs.brown.edu/mailman/listinfo/plt-dev" target="_blank">http://list.cs.brown.edu/mailman/listinfo/plt-dev</a><br> ><br><br><br><br></div></div> <div class="im">--<br>Jay McCarthy <<a href="mailto:jay@cs.byu.edu">jay@cs.byu.edu</a>><br>Assistant Professor / Brigham Young University<br><a href="http://teammccarthy.org/jay" target="_blank">http://teammccarthy.org/jay</a><br> <br>"The glory of God is Intelligence" - D&C 93<br>_________________________________________________<br></div> <div> <div></div> <div class="h5"> For list-related administrative tasks:<br> <a href="http://list.cs.brown.edu/mailman/listinfo/plt-dev" target="_blank">http://list.cs.brown.edu/mailman/listinfo/plt-dev</a><br></div></div></blockquote></div> <br>