Re: [racket-dev] Updating dependency packages from other sources
> If I try to remove just the `x11` package so I can replace it, I get > this error: > > $ raco pkg remove x11 > raco pkg remove: cannot remove packages that are dependencies of other > packages > dependencies: >x11 (required by: (aosd)) It would be nice if this error message appended a hint like: You can remove the package anyway with --force. In fact maybe that's sufficient, don't really need a new `replace' subcommand. Even with a new `replace', the hint would still be handy (and should also mention `replace'?) because folks will probably first try to do what Asumu did? On Thu, Aug 15, 2013 at 11:07 AM, Asumu Takikawa wrote: > On 2013-08-15 08:19:06 -0600, Jay McCarthy wrote: >> As for what we could do going forward, I think either of these >> approaches could be 'automated'. > > Yes, that'd be great. > >> For instance, we could add a command like >> >> $ raco pkg replace x11 new-x11-source >> >> This would behave like either of those (which would be invisible to the >> user). >> >> Do you have any opinions about how you'd want to do this replacement? > > Maybe `raco pkg install` can have an additional flag that lets you > replace existing packages? Or maybe it should allow conflicts if the > package has the same name as an already installed package (possibly > prompting/warning the user)? > > Cheers, > Asumu > _ > Racket Developers list: > http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Updating dependency packages from other sources
On 2013-08-15 08:19:06 -0600, Jay McCarthy wrote: > As for what we could do going forward, I think either of these > approaches could be 'automated'. Yes, that'd be great. > For instance, we could add a command like > > $ raco pkg replace x11 new-x11-source > > This would behave like either of those (which would be invisible to the user). > > Do you have any opinions about how you'd want to do this replacement? Maybe `raco pkg install` can have an additional flag that lets you replace existing packages? Or maybe it should allow conflicts if the package has the same name as an already installed package (possibly prompting/warning the user)? Cheers, Asumu _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Updating dependency packages from other sources
I don't think there's any good way to do this now. Here are ways that will work: 1) Ignore the dependency during removal $ raco pkg remove --force x11 $ raco pkg install new-x11-source 2) Manually change the source in yours package database and then update $ emacs $PLTHOME/racket/share/pkgs/pkgs.rktd $ raco pkg update x11 As for what we could do going forward, I think either of these approaches could be 'automated'. For instance, we could add a command like $ raco pkg replace x11 new-x11-source This would behave like either of those (which would be invisible to the user). Do you have any opinions about how you'd want to do this replacement? Jay On Tue, Aug 13, 2013 at 9:48 PM, Asumu Takikawa wrote: > Hi all, > > I have a question about updating packages. I'll use an example > development scenario to frame the question. > > Suppose I have package `aosd` installed that depends on `x11`: > > Installation-wide: >Package ChecksumSource >x11 0fc7555f6bc8f09601a75f9d88f44bfa3c4ff632(catalog > x11) >aosd 7ab51262a256a324b062d7b407cb5341d1f41f69(catalog > aosd) > > Now suppose I want to work on the `x11` package since I need to upgrade > it for some aspect of the `aosd` package. Right now it's installed from > the package server, but I want to switch it to a linked package from the > filesystem for development. > > If I try to remove just the `x11` package so I can replace it, I get > this error: > > $ raco pkg remove x11 > raco pkg remove: cannot remove packages that are dependencies of other > packages > dependencies: >x11 (required by: (aosd)) > > which is reasonable. But I have to remove the package before I can > install it from a different source. The `raco pkg update` command looks > like it might help, but it doesn't let you update from a different > source AFAICT. The `raco pkg install` command won't work because it'd be > a conflicting package. > > What are the right steps to install over dependency packages? I don't > think manually uninstalling and re-installing is a good solution. If n > other packages depended on `x11` too, it seems like I'd have to > re-install all n of them. > > Cheers, > Asumu > _ > Racket Developers list: > http://lists.racket-lang.org/dev -- Jay McCarthy Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Fishy directory rename
Does it not make sense to you that someone might want to use htdp without using the tests? As for the docs, the split there is so that someone can produce a package that re-uses the implementation of the teaching languages without focusing all clients to get and install the documentation. Think of someone writing a universe game in the final project and then wanting to share it with others. Sure seems reasonable to me. Robby On Thu, Aug 15, 2013 at 8:43 AM, Matthias Felleisen wrote: > > Eli is right in that I did not intend this directory to be a real test. It > is definitely misnamed. But it's no big deal so let's leave it as is. > > [[ As I have written privately, I just do not understand the split of htdp > into three different packages but so be it. ]] > > -- Matthias > > > > On Aug 14, 2013, at 9:17 PM, Robby Findler wrote: > > I moved that because I thought it was a test. I thought it was a test > because of the directory name and because it has files that are not being > compiled. > > (But I didn't check with Matthias specifically about that directory.) > > Robby > > > On Wed, Aug 14, 2013 at 8:02 PM, Eli Barzilay wrote: > >> Trying to sort out some apparent mess in the props, I ran into this >> possibly bad rename: >> >> pkgs/htdp-pkgs/htdp-lib/2htdp/utest >> --> >> pkgs/htdp-pkgs/htdp-test/2htdp/utest >> >> Before the move, the "utest" directory was not considered a test by >> the old distribution rules (since it wasn't in a "tests" directory), >> and after the move it is in a *-test package and therefore probably >> considered as tests that wouldn't be packaged in the release. >> >> I *think* that it's wrong, because I vaguely remember Matthias saying >> that he wants "utest" in the distribution, but I'm not sure. >> >> [The more disturbing point is that dealing with two of these paths and >> comparing it with the old paths made this thing ridiculously difficult >> to notice.] >> >> -- >> ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: >> http://barzilay.org/ Maze is Life! >> _ >> Racket Developers list: >> http://lists.racket-lang.org/dev >> > > _ > Racket Developers list: > http://lists.racket-lang.org/dev > > > _ Racket Developers list: http://lists.racket-lang.org/dev
Re: [racket-dev] Fishy directory rename
Eli is right in that I did not intend this directory to be a real test. It is definitely misnamed. But it's no big deal so let's leave it as is. [[ As I have written privately, I just do not understand the split of htdp into three different packages but so be it. ]] -- Matthias On Aug 14, 2013, at 9:17 PM, Robby Findler wrote: > I moved that because I thought it was a test. I thought it was a test because > of the directory name and because it has files that are not being compiled. > > (But I didn't check with Matthias specifically about that directory.) > > Robby > > > On Wed, Aug 14, 2013 at 8:02 PM, Eli Barzilay wrote: > Trying to sort out some apparent mess in the props, I ran into this > possibly bad rename: > > pkgs/htdp-pkgs/htdp-lib/2htdp/utest > --> > pkgs/htdp-pkgs/htdp-test/2htdp/utest > > Before the move, the "utest" directory was not considered a test by > the old distribution rules (since it wasn't in a "tests" directory), > and after the move it is in a *-test package and therefore probably > considered as tests that wouldn't be packaged in the release. > > I *think* that it's wrong, because I vaguely remember Matthias saying > that he wants "utest" in the distribution, but I'm not sure. > > [The more disturbing point is that dealing with two of these paths and > comparing it with the old paths made this thing ridiculously difficult > to notice.] > > -- > ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: > http://barzilay.org/ Maze is Life! > _ > Racket Developers list: > http://lists.racket-lang.org/dev > > _ > Racket Developers list: > http://lists.racket-lang.org/dev _ Racket Developers list: http://lists.racket-lang.org/dev
