There are no plans for the Racket maintainers to host package sources, binaries, or histories for any packages that are not required by the main-distribution package. (And even for those, we do not host sources (we use Github) and we do not store arbitrary histories, just releases.)
Package catalogs (such as pkgs.racket-lang.org) only store references to packages stored elsewhere. Among other things, this promotes flexibility, decentralizes work, and insulates us from an licensing and copyright issues. We encourage all package authors to use long-lived hosting of all versions. The use of Git (whether a personal server, Github, Bitbucket, etc) automatically provides historical versions. We welcome submission of pull requests to add support for Mercurial or other similar repositories. If both of these are not possible for you for some reason, the package API supports HTTP-accessible directories, so you can just have a directory of files on a site somewhere. (For instance, the main-distribution packages are served on such a directory hosted by Amazon S3.) We have no plans to disallow or otherwise censure packages that don't do this. However, we expect that the free access to multiple options (Github & Bitbucket) will be its own encouragement of this activity. If someone in the community would like to start their own site to store old versions, we have no comment on their activity and will consider pull requests that make their job easier. Jay On Sat, Dec 5, 2015 at 5:59 PM, Neil Van Dyke <[email protected]> wrote: > Any ideas for ensuring that all "released versions" of non-core Racket > packages in the new package system remain accessible (short-term, and > long-term)? > > Ideas other than the current ad-hoc people individually copying&preserving > the versions that they use or anticipate someday using (which, incidentally, > tends to result in lazy copy&paste&modify, rather than shared reusable > components). > > And, ideas other than "just use github". (Though one could make some > pragmatic arguments for that, but I'm interested in alternatives.) > > One idea is for the "packages.racket-lang.org" server to double as a server > of all current and past versions of packages, like was done for PLaneT. > > Neil V. > > -- > 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/56636C4B.3030909%40neilvandyke.org. > For more options, visit https://groups.google.com/d/optout. -- Jay McCarthy Associate Professor PLT @ CS @ UMass Lowell http://jeapostrophe.github.io "Wherefore, be not weary in well-doing, for ye are laying the foundation of a great work. And out of small things proceedeth that which is great." - D&C 64:33 -- 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/CAJYbDakECn4UJ2Z1BgkbFx8%2B1KBv1J0jEZcFcUsu%2BN9Sg%3DKNXg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
