The Northwestern natipkg build will be changed to be a CS build so I
believe that means that the pkg builds will now running on top of CS (and
otherwise unchanged).

Robby


On Tue, Sep 29, 2020 at 2:41 PM Sam Tobin-Hochstadt <sa...@cs.indiana.edu>
wrote:

> How will this affect the pkg-build snapshots?
>
> Sam
>
> On Tue, Sep 29, 2020 at 3:33 PM Robby Findler <ro...@cs.northwestern.edu>
> wrote:
> >
> > I'm finally catching up and switching the Northwestern snapshots to BC
> by default. I've made the change and the changes will kick off tonight at
> midnight, Chicago time (probably failing horribly but maybe in a week or
> two we'll be back in business and the next paragraph will be accurate when
> that all settles).
> >
> > All of the existing links should continue to work (let me know if you
> notice that didn't happen) but they will generally be CS where they were BC
> builds before. In particular, we're going to continue to have windows BC
> and CS, 64 and 32 bit builds; 64 bit BC and CS Mac OS builds, and 32 bit BC
> Mac OS builds. I've added Debian 64 bit CS builds, so we'll have 64 bit BC
> and CS as well as 32 bit BC builds for debian. For the rest, the 64 bit
> versions will all become CS builds and the 32 bit versions will all stay BC.
> >
> > There will be explicit links ending with -bc and -cs as well as aliases
> that do not include the VM specifier that go to whatever is available, as
> Matthew describes for the Utah snapshots and "min-racket" will also change
> to "racket-minimal" (but still with an alias to avoid breaking old links).
> >
> > Robby
> >
> >
> > On Tue, Aug 11, 2020 at 5:24 PM Matthew Flatt <mfl...@cs.utah.edu>
> wrote:
> >>
> >> As you may know, the Racket Git repo recently switched to Racket CS as
> >> the default build. That is, if you check out the repo and `make`, then
> >> you get an in-place Racket CS build instead of Racket BC.
> >>
> >> The next step in moving toward Racket CS is to try switching the
> >> snapshot builds. Out current plan is to switch the Utah build on August
> >> 13. The Northwestern snapshot build will be unchanged, for now. This
> >> change will have no effect on the regular, release downloads.
> >>
> >> The layout of the page at
> >>
> >>  https://www.cs.utah.edu/plt/snapshots/
> >>
> >> will change so that CS and BC builds are grouped together, more like
> >> the Northwestern snapshot layout, but an installer that doesn't have
> >> "BC" in its link will download a Racket CS installer.
> >>
> >> If you have an automated process that pulls from the snapshot site,
> >> then it probably downloads something like
> >>
> >>
> https://www.cs.utah.edu/plt/snapshots/current/installers/racket-current-x86_64-linux-precise.sh
> >>
> >> As of August 13, that will download a Racket CS installer instead of a
> >> BC installer, because there's no "-bc" suffix in the name.
> >>
> >> Racket BC builds will still be available; you'll just have to
> >> specifically select a download option with "BC" in the link name or
> >> "-bc" in the URL. For example,
> >>
> >>
> https://www.cs.utah.edu/plt/snapshots/current/installers/racket-current-x86_64-linux-precise-bc.sh
> >>
> >> will download a Racket BC installer. For now, 32-bit Windows and Mac OS
> >> installers will be available only for BC, because we view those as
> >> legacy platforms.
> >>
> >> For consistently, you'll be able to access the CS installers using a
> >> "-cs" suffix. The installer name without a "-cs" or "-bc" suffix is an
> >> aliases for one with "-cs". Of course, the "current" names are all
> >> aliases for installers that have a specific version number.
> >>
> >> While we're adjusting installer names, the canonical name for Minimal
> >> Racket installers will change to "racket-minimal-..." instead of
> >> "min-racket-...". The new name matches the names used for releases. For
> >> the foreseeable future, "min-racket-..." aliases will still work, but
> >> you should migrate to "racket-minimal-..." if you have an automated
> >> process that uses "min-racket-...".
> >>
> >>
> >> Matthew
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "Racket Users" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an email to racket-users+unsubscr...@googlegroups.com.
> >> To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-users/20200811162420.18d%40sirmail.smtps.cs.utah.edu
> .
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Racket Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to racket-users+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/racket-users/CAL3TdOOw%2BBkMj%2B-vN_mfbe%2Bt2MMuwuVtpyQDJyeOUoyjOWkHpA%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to racket-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/racket-users/CAL3TdOM2YAHMVExWnnFznWy77%3DOnbo3T5F8eVwpakxBgy1%2BtTA%40mail.gmail.com.

Reply via email to