At Thu, 13 Jun 2013 17:56:52 -0400, Sam Tobin-Hochstadt wrote:
> * The error message when you look for a missing collection is really
> long if you have a lot of packages installed
Yes. I have been thinking about whether there's a better solution than
just not showing the paths, but I can just dro
Thanks, Jay. I have two high-level negative comments.
1) I don't think that it is feasible to aim for a world where 'raco setup'
never errors. (The real-world variation of your matthew-isnt-looking
example is system-specific code and we do do that a bunch.)
2) You are currently making a distincti
On Jun 14, 2013, at 10:49 AM, Jay McCarthy wrote:
> Another idea is to make it so that 'raco setup' can have a mode where
> it passes error structures back that contain the paths (so 'raco pkg'
> knows where they are and which package directory it was) rather than
> just printing error messages.
On Fri, Jun 14, 2013 at 8:40 AM, Carl Eastlund wrote:
> Jay,
>
> Thanks for the detailed summary. Right now I think the biggest missing
> piece of information when something goes wrong is "which packages were
> affected?". If I download package A, and it pulls in B and C, and they pull
> in D, E
Jay,
Thanks for the detailed summary. Right now I think the biggest missing
piece of information when something goes wrong is "which packages were
affected?". If I download package A, and it pulls in B and C, and they
pull in D, E, and F, and then somewhere along the lines raco setup fails, I
no
I'll try to respond to these four messages at the same time...
Sam said,
> In addition to the larger point Robby makes, this can be pretty
> confusing. For example, you can fail to install enough dependencies,
> I think.
>
> Another problem is that there's no way to know what to do to fix
> thing
On Fri, Jun 14, 2013 at 6:19 AM, Sam Tobin-Hochstadt wrote:
> On Thu, Jun 13, 2013 at 10:56 PM, Jay McCarthy wrote:
>> On Thu, Jun 13, 2013 at 3:56 PM, Sam Tobin-Hochstadt
>> wrote:
>>> * The error message when you look for a missing collection is really
>>> long if you have a lot of packages i
True, but in this case, the code that is doing that reading knows what
the package was and could give a good error message.
Jay
On Thu, Jun 13, 2013 at 9:13 PM, Robby Findler
wrote:
> WRT to the stacktrace below, I guess that if the info.rkt file had been in a
> suggestively named directory, e.g
On Thu, Jun 13, 2013 at 10:56 PM, Jay McCarthy wrote:
> On Thu, Jun 13, 2013 at 3:56 PM, Sam Tobin-Hochstadt
> wrote:
>> As part of my experiment in creating a different split of the
>> repository into packages, I spent some time working with the new setup
>> for building Racket, and cut myself
I know it runs it. I don't know why Jay writes "The package system says
something is installed when the files are in place and the link is made.
>From some perspective, that's its job.". I can't tell if there's some
technical piece I'm missing or not (on the surface, these words sound
almost lazy b
It does run 'raco setup', it just doesn't have much to do in response to a
failure, at least right now.
Carl Eastlund
On Thu, Jun 13, 2013 at 11:14 PM, Robby Findler wrote:
> Also, Jay: can you explain more why 'raco setup' isn't something that we
> should think about as running "inside" the pk
Also, Jay: can you explain more why 'raco setup' isn't something that we
should think about as running "inside" the pkg manager? (I'm not saying
that automatically rolling back packages is the right thing to do or
anything like that, but I would like to understand the model you have
better.)
Robby
WRT to the stacktrace below, I guess that if the info.rkt file had been in
a suggestively named directory, e.g.,
/var/tmp/pkg13711534991371153499937/future-visualizer/info.rkt
(assuming that the package's name was future-visualizer) that might have
been a useful clue.
Robby
On Thu, Jun 13, 20
On Thu, Jun 13, 2013 at 3:56 PM, Sam Tobin-Hochstadt wrote:
> As part of my experiment in creating a different split of the
> repository into packages, I spent some time working with the new setup
> for building Racket, and cut myself on many of it's rough edges. Some
> of these are about the pac
As part of my experiment in creating a different split of the
repository into packages, I spent some time working with the new setup
for building Racket, and cut myself on many of it's rough edges. Some
of these are about the package system in general, and some are about
the new repository and bui
15 matches
Mail list logo
