Robby, I don't know if this is good enough, but I was considering, based on Matt's feedback, to call your ring-0 packages "main distribution collections" and those that might be a bit suspect and still attribute to individuals, rather than being blessed as part of the distributions, as "contributed collections". I'm suggesting placing emphasis on 'collection' rather than package, as I see a package as a vehicle for distributing collections (for the most part). Other vehicles also exist for making collections native to the installation. Accordingly one would be able to say things like "if you want the X collection, then go get the Y package - that is the best way to do it. ... The Y package will also give you the Z collection, and the A and B modules that will be added to .."
Don't know, this nomenclatures seems to work for what you are getting at. On Thursday, April 30, 2015 at 10:56:58 PM UTC+8, robby wrote: > > Thomas: thank you for helping to clean all this up! It's quite welcome. > > One thing to consider: if it is at all possible, I think it would be > good if we tried to focus on a distinction between collections from > ring-0 packages and those that aren't instead of a distinction between > collections from pkgs that come from particular authors. That is, one > thing we'd like to do is to make distinctions between pkgs that work > well and those that don't instead of distinctions between pkgs that > come from centralized place or are distinguished only because of some > notion of "privilege", instead of some approximation to "quality". > > Robby > > On Thu, Apr 30, 2015 at 9:39 AM, Thomas Lynch > <[email protected] <javascript:>> wrote: > > > > for the rest of this, I think I better study this some more before > typing > > too much on the docs. I'll just try to get this into module-basics for > the > > new reader (such as myself). > > > > Thanks for that understanding of library. > > > > The term 'standard lib' made me wince when I wrote it, just didn't know > a > > better way to say it. Main distribution collection. Thanks. And the > > collections installed later? Perhaps add-on collections or some such? > Then > > taken together the collections with modules that can be accessed without > > quotes (or via #lang) are ___ collections. > > > > If for the blank we insert installed collections, then there is > conflation > > with install as a process, and as an adjective for a package or other > file > > that was used in that process (as described earlier). It is even > difficult > > to disambiguate with an explanation. Seems like the term used for this > > concept in other language contexts is library. User stuff, and library > > stuff. hmm main distribution library. Additional libraries. > Access > > library stuff with unquoted arg on require, or #lang. But library has > > another meaning already. > > > > How about 'native collections' and 'local collections'. Native > collections > > come in two flavors, main distribution, and contributed. A collection > is > > made native through the process of installing it. If it is installed > via > > adding a directory to the catalog then the installed collection can not > be > > deleted as racket will use it directly. If it is installed via a > package, > > then the installed package can be deleted. native/local .. other word > > pairs can work here. suggestions? > > > > So then when talking about native/local or installation, emphasis is on > > collections rather than on modules. The understanding is that the > module > > inherits its native/local status by virtue of 'being in the collection'. > If > > it is in a native collection then when using require is accessed without > > quotes. If it is local then it is accessed with quotes. > > > > ... though there is a nuance with packages where installation might take > a > > scatter shot and put modules in more than one collection. Still only > native > > modules will be affected. > > > > Would this native/local thing be good racket speak? > > > > > > > > > > > > > > > > > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "Racket Developers" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to [email protected] <javascript:>. > > To post to this group, send email to [email protected] > <javascript:>. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/racket-dev/9c9689ed-76a6-47ec-99f4-97e366f5f01f%40googlegroups.com. > > > > > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/2f51a866-5a4b-4c2e-9b63-bd4b8a5c678e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
