Op Wed, 19 Oct 2005 17:17:15 -0400 (EDT) schreef Igor Pechtchanski
in Pine.GSO.4.63.0510191712430.409atslinky.cs.nyu.edu:
: On Tue, 18 Oct 2005, Bas Buzz van Gompel wrote:
:
: Op Tue, 18 Oct 2005 01:35:12 -0400 (EDT) schreef Igor Pechtchanski:
: : On Tue, 18 Oct 2005, Buzz wrote:
:
: : Op
On Friday, October 14, 2005 Igor wrote:
On Oct 14 03:30, Brian Dessent wrote:
What I had in mind was something like this:
-
Warning: The mirror you have selected is not on the list
of official Cygwin
On Tue, 18 Oct 2005, Bas Buzz van Gompel wrote:
Op Tue, 18 Oct 2005 01:35:12 -0400 (EDT) schreef Igor Pechtchanski:
: On Tue, 18 Oct 2005, Buzz wrote:
: Op Sun, 16 Oct 2005 17:30:34 -0400 (EDT) schreef Igor Pechtchanski:
[Mirror manually added or stale.]
: : You are assuming that the
Op Tue, 18 Oct 2005 01:35:12 -0400 (EDT) schreef Igor Pechtchanski
in [EMAIL PROTECTED]:
: On Tue, 18 Oct 2005, Buzz wrote:
: Op Sun, 16 Oct 2005 17:30:34 -0400 (EDT) schreef Igor Pechtchanski:
[Mirror manually added or stale.]
: : You are assuming that the format of the last-mirror file is
I'm thinking an asterisk after the name (with
dialog text explaining its meaning), since using color
becomes confusing
when you also have the selected/not-selected color distinction.
If the warning color were red, you could make the selected
color white
on red instead of the Windows
Op Sun, 16 Oct 2005 17:30:34 -0400 (EDT) schreef Igor Pechtchanski
in [EMAIL PROTECTED]:
: On Fri, 14 Oct 2005, Brian Dessent wrote:
:
: Brian Dessent wrote:
:
: Except, from the standpoint of setup there is no way to distinguish the
: following two scenarios:
:
: That is, unless you meant
On Tue, 18 Oct 2005, Buzz wrote:
Op Sun, 16 Oct 2005 17:30:34 -0400 (EDT) schreef Igor Pechtchanski:
: On Fri, 14 Oct 2005, Brian Dessent wrote:
:
: Brian Dessent wrote:
:
: Except, from the standpoint of setup there is no way to distinguish the
: following two scenarios:
:
: That
On Fri, 14 Oct 2005, Brian Dessent wrote:
Brian Dessent wrote:
Except, from the standpoint of setup there is no way to distinguish the
following two scenarios:
That is, unless you meant mirror that was manually added *this
session*, whereas I was interpreting it to be user manually
Igor Pechtchanski wrote:
Technically, these packages *do* require bash, and coreutils, and possibly
others, so automatic dependency detection is hard (we don't want to have
setup parse shell scripts). Perhaps we should augment the depends
function of the g-b-s to also look at the postinstall
On Oct 13 22:19, Christopher Faylor wrote:
Is there any way that my proposal of adding a check to see if the currently
selected mirror is in the list of mirrors and issuing a pop-up warning if
not, could be implemented?
I suppose that this would have to be defeatable for people who want to
Corinna Vinschen wrote:
Is there any way that my proposal of adding a check to see if the currently
selected mirror is in the list of mirrors and issuing a pop-up warning if
not, could be implemented?
I suppose that this would have to be defeatable for people who want to
use setup.exe
On Oct 14 03:30, Brian Dessent wrote:
Corinna Vinschen wrote:
Is there any way that my proposal of adding a check to see if the
currently
selected mirror is in the list of mirrors and issuing a pop-up warning if
not, could be implemented?
I suppose that this would have to be
On Thu, 13 Oct 2005, Brian Dessent wrote:
Igor Pechtchanski wrote:
Technically, these packages *do* require bash, and coreutils, and possibly
others, so automatic dependency detection is hard (we don't want to have
setup parse shell scripts). Perhaps we should augment the depends
On Fri, 14 Oct 2005, Corinna Vinschen wrote:
On Oct 14 03:30, Brian Dessent wrote:
Corinna Vinschen wrote:
Is there any way that my proposal of adding a check to see if the
currently
selected mirror is in the list of mirrors and issuing a pop-up warning
if
not, could be
On Fri, Oct 14, 2005 at 09:19:01AM -0400, Igor Pechtchanski wrote:
On Fri, 14 Oct 2005, Corinna Vinschen wrote:
On Oct 14 03:30, Brian Dessent wrote:
Corinna Vinschen wrote:
Is there any way that my proposal of adding a check to see if the
currently
selected mirror is in the
On Oct 14 10:44, Christopher Faylor wrote:
On Fri, Oct 14, 2005 at 09:19:01AM -0400, Igor Pechtchanski wrote:
On Fri, 14 Oct 2005, Corinna Vinschen wrote:
On Oct 14 03:30, Brian Dessent wrote:
Corinna Vinschen wrote:
I suppose that this would have to be defeatable for people who want
Corinna Vinschen wrote:
To reiterate, I think that it makes sense to differ between a
*manually added* mirror and a chosen mirror from the official mirror
list, which is just dead or comatose or something.
Manually added mirrors are usually either company mirrors or in some
other way under
Brian Dessent wrote:
Except, from the standpoint of setup there is no way to distinguish the
following two scenarios:
That is, unless you meant mirror that was manually added *this
session*, whereas I was interpreting it to be user manually entered a
non-official mirror at some point in the
On 10/14/2005 5:15 PM, Brian Dessent wrote:
I like the idea of Don't show this again option because it's a
standard dialog item that people are familiar with, and it makes it easy
for them to acknowledge that they might be doing something wrong but
they don't want to be pestered about it every
Brian Dessent wrote:
Except, from the standpoint of setup there is no way to distinguish the
following two scenarios:
A) User knowingly uses local company mirror, or uses a non-official
mirror to install non-official packages.
B) 2 years ago, user chose a mirror located on a ISDN line in Outer
Warren Young wrote:
The the mirror list could show nonstandard mirrors in a different color.
But every mirror in the mirrors.lst is an official mirror. There can be
at most only one mirror URL in the dialog that is not official: the one
that the user has just typed in, or the one that was used
Brian Dessent wrote:
There can be
at most only one mirror URL in the dialog that is not official:
Ah. I didn't know that limitation.
I'm thinking an asterisk after the name (with
dialog text explaining its meaning), since using color becomes confusing
when you also have the
Igor, I'm very thankful to have patches from you, and I appreciate that
you're contributing. I seriously need to work on being more timely
about this.
Igor Pechtchanski wrote:
Here's a list of setup patches I submitted in September:
http://cygwin.com/ml/cygwin-apps/2005-09/msg00502.html
Brian Dessent wrote:
Go ahead and commit those. And again, thanks.
I meant to add:
Please add a couple of lines to the CHANGES file to describe the
bugfixes / new features. What I'm aiming for here is to have something
that is not as terse as the ChangeLog that summarizes changes in plain
On Thu, Oct 13, 2005 at 02:12:14PM -0700, Brian Dessent wrote:
Igor, I'm very thankful to have patches from you, and I appreciate that
you're contributing. I seriously need to work on being more timely
about this.
Igor Pechtchanski wrote:
Here's a list of setup patches I submitted in
On Thu, 13 Oct 2005, Brian Dessent wrote:
Igor, I'm very thankful to have patches from you, and I appreciate that
you're contributing. I seriously need to work on being more timely
about this.
It's okay, I just wanted to make sure they didn't get lost in the noise...
I've applied the
26 matches
Mail list logo