Merging the `net` and `compiler` repositories back in
59 views
Skip to first unread message
Sam Tobin-Hochstadt
May 25, 2016, 4:25:24 PM5/25/16
to d...@racket-lang.org
When we split the Racket repository out into many smaller
repositories, we were quite aggressive -- just about everything moved
out. At this point, it's clear that we were a little too aggressive.
In particular, the `net` and `compiler` repositories have been uneasy
as separate entities. Their docs are in the wrong places, and they
often have to change in coordination with the main repo. So we're
going to merge them back in.
You can see how this will work in this pull request:
https://github.com/racket/racket/pull/1332
The resulting repository will have multiple root commits. I don't
think this is a problem, but it can perhaps be fixed if needed.
Once this is done, previously cloned versions of those repositories
won't update. To address this, run the following command now, unless
you absolutely need the clone versions:
$ raco pkg update --lookup net compile
I plan to merge this in the next couple days.
Sam
repositories, we were quite aggressive -- just about everything moved
out. At this point, it's clear that we were a little too aggressive.
In particular, the `net` and `compiler` repositories have been uneasy
as separate entities. Their docs are in the wrong places, and they
often have to change in coordination with the main repo. So we're
going to merge them back in.
You can see how this will work in this pull request:
https://github.com/racket/racket/pull/1332
The resulting repository will have multiple root commits. I don't
think this is a problem, but it can perhaps be fixed if needed.
Once this is done, previously cloned versions of those repositories
won't update. To address this, run the following command now, unless
you absolutely need the clone versions:
$ raco pkg update --lookup net compile
I plan to merge this in the next couple days.
Sam
Leif Andersen
May 25, 2016, 4:58:15 PM5/25/16
to Sam Tobin-Hochstadt, d...@racket-lang.org
Please ping this mailing list after you've merged it in, so that
people (me anyway) who heavily use the `racket-compiler` package can
act accordingly.
~Leif Andersen
> --
> 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 racket-dev+...@googlegroups.com.
> To post to this group, send email to racke...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAK%3DHD%2BabXU4FExBCxX1bMe7Y%3DX3UqoTt9%2BNaRXrvBCPW4aSS6g%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
people (me anyway) who heavily use the `racket-compiler` package can
act accordingly.
~Leif Andersen
> 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 racket-dev+...@googlegroups.com.
> To post to this group, send email to racke...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAK%3DHD%2BabXU4FExBCxX1bMe7Y%3DX3UqoTt9%2BNaRXrvBCPW4aSS6g%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
Matthias Felleisen
May 25, 2016, 9:13:01 PM5/25/16
to Sam Tobin-Hochstadt, d...@racket-lang.org
> % raco pkg update --lookup net compile
> raco pkg update: package not currently installed
> package: compile
> current scope: installation
Next, does the “won’t update” mean we have to clone a completely new version?
What do I do with un-pushed commits? (I am not ready to push.)
Thanks — Matthias
Robby Findler
May 26, 2016, 12:52:49 AM5/26/16
to Matthias Felleisen, Sam Tobin-Hochstadt, d...@racket-lang.org
Maybe there is a missing "r" in Sam's commandline?
Robby
Robby
> --
> 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 racket-dev+...@googlegroups.com.
> To post to this group, send email to racke...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/2D26007F-587F-4726-808B-A6CB3515EF54%40ccs.neu.edu.
> 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 racket-dev+...@googlegroups.com.
> To post to this group, send email to racke...@googlegroups.com.
Matthias Felleisen
May 26, 2016, 7:38:15 AM5/26/16
to Robby Findler, Sam Tobin-Hochstadt, d...@racket-lang.org
On May 26, 2016, at 12:52 AM, Robby Findler <ro...@eecs.northwestern.edu> wrote:Maybe there is a missing "r" in Sam's commandline?
Robby
Cool.
% raco pkg update --lookup net compiler
00: Resolving "net" via https://pkgs.racket-lang.orgResolving "net-lib" via https://pkgs.racket-lang.orgResolving "net-doc" via https://pkgs.racket-lang.orgResolving "compiler" via https://pkgs.racket-lang.orgResolving "compiler-lib" via https://pkgs.racket-lang.orgResolving "zo-lib" via https://pkgs.racket-lang.orgNo updates available
My remaining questions stand:
— Does the “won’t update” mean we have to clone a completely new version?
Sam Tobin-Hochstadt
May 26, 2016, 10:38:31 AM5/26/16
to Matthias Felleisen, d...@racket-lang.org
On Wed, May 25, 2016 at 9:12 PM, Matthias Felleisen
% raco pkg update --lookup net compiler
> Next, does the “won’t update” mean we have to clone a completely new version?
No, your existing clone of the `racket` repository will get the new
changes to net/compiler/etc. If you have a snapshot, and a clone of
net, that will not get new updates unless you run the command above.
> What do I do with un-pushed commits? (I am not ready to push.)
Commits to the `racket` repository should be fine. Are your commits to
the `net` or `compiler` repositories?
Sam
<matt...@ccs.neu.edu> wrote:
>
>> On May 25, 2016, at 4:25 PM, Sam Tobin-Hochstadt <sa...@cs.indiana.edu> wrote:
>>
>
>> On May 25, 2016, at 4:25 PM, Sam Tobin-Hochstadt <sa...@cs.indiana.edu> wrote:
>>
> Could you explain to the uninitiated what the meaning of the result is?
>
>> % raco pkg update --lookup net compile
>> raco pkg update: package not currently installed
>> package: compile
>> current scope: installation
This was missing an `r` as Robby suggested. The correct command line is:
>
>> % raco pkg update --lookup net compile
>> raco pkg update: package not currently installed
>> package: compile
>> current scope: installation
% raco pkg update --lookup net compiler
> Next, does the “won’t update” mean we have to clone a completely new version?
No, your existing clone of the `racket` repository will get the new
changes to net/compiler/etc. If you have a snapshot, and a clone of
net, that will not get new updates unless you run the command above.
> What do I do with un-pushed commits? (I am not ready to push.)
the `net` or `compiler` repositories?
Sam
Sam Tobin-Hochstadt
May 27, 2016, 6:50:23 PM5/27/16
to d...@racket-lang.org
This is now complete. Let me know if you experience any trouble
building in the next couple days, and I'll try to fix the problem.
Sam
building in the next couple days, and I'll try to fix the problem.
Sam
Reply all
Reply to author
Forward
0 new messages