Hello Robert,
Wednesday, June 26, 2002, 11:54:05 PM, you wrote:
RC Key changes:
RC * Feedback on MD5 processing.
RC * Feedback on parsing progress.
These are cool! :)
Now I've noticed something, though it is not a regression - the
2.249.2.4 has the same behaviour:
1. Select 'Install from
AFAICT http://prdownloads.sf.net/kde-cygwin/setup.ini is not a valid
setup.ini.
It's a redirect page of some sort.
It shouldn't crash setup, and setup-HEAD doesn't crash. You could try the
setup available from http://www.cygwin.com/setup-snapshots.
Rob
- Original Message -
From:
- Original Message -
From: Pavel Tsekov [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 27, 2002 7:57 PM
Subject: Re: New setup snapshot and changes
Hello Robert,
Wednesday, June 26, 2002, 11:54:05 PM, you wrote:
RC Key changes:
RC * Feedback on MD5 processing.
RC
[Per instructions at http://kde-cygwin.sourceforge.net/kde2.php]
On Thu, Jun 27, 2002 at 08:02:47PM +1000, Robert Collins wrote:
AFAICT http://prdownloads.sf.net/kde-cygwin/setup.ini is not a valid
setup.ini.
It's a redirect page of some sort.
Yes. They've been screwed by the download
- Original Message -
From: John Marshall [EMAIL PROTECTED]
To: Robert Collins [EMAIL PROTECTED]
It sounds very good to me! So add syntax (or just more parsing because
it's already there?) to mirrors.lst so setup.exe could display stuff
like
http://foonet.no (Norway)
Cool :-).
John Marshall wrote:
Yes. They've been screwed by the download mirror system Sourceforge
introduced on 2002-05-03. As I wrote when I changed prc-tools's
.htaccess to deal with this:
Update the redirect to cope with Sourceforge's new download
mirror system. You'd think
AFAICT http://prdownloads.sf.net/kde-cygwin/setup.ini is not a valid
setup.ini.
Rob, where is the problem with it. I have updated it after your last hints. Does
I have forgotten something ?
Ralf
- Original Message -
From: Ralf Habacker [EMAIL PROTECTED]
To: Cygwin-Apps [EMAIL PROTECTED]
Sent: Thursday, June 27, 2002 9:20 PM
Subject: RE: new setup.exe crashes with kde's setup.ini
AFAICT http://prdownloads.sf.net/kde-cygwin/setup.ini is not a valid
setup.ini.
Rob, where
- Original Message -
From: John Marshall [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 27, 2002 8:24 PM
That works fine in 2.249.2.4 but has a parse error in the 2.253
snapshot, perhaps because of the blank line at the end.
(Hey, nice parse error message! That'll
On Thu, Jun 27, 2002 at 09:27:47PM +1000, Robert Collins wrote:
(Hey, nice parse error message! That'll help if the bizarre parse error
prc-tools's setup.ini was intermittently getting recurs.)
Errm, Are you being sarcastic or literal here? I didn't mean to improve the
parse error
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of John Marshall
Sent: Thursday, 27 June 2002 9:36 PM
To: [EMAIL PROTECTED]
Subject: Re: new setup.exe crashes with kde's setup.ini
On Thu, Jun 27, 2002 at 09:27:47PM +1000, Robert Collins wrote:
On Thu, Jun 27, 2002 at 08:25:29PM +1000, Robert Collins wrote:
That change seems like something easily big enough for HEAD, and
probably it'd be over the threshold that I'd need to be copyright-
assigned. That's doable, but it'll take time of course.
Copyright assignment isn't needed for
On Wed, Jun 26, 2002 at 12:46:30PM -0400, Prentis Brooks wrote:
As you wish *grin*
http://www.stonegard.com/cygwin/tcp_wrappers_7.6/tcp_wrappers-7.6-1-src.tar.bz2
http://www.stonegard.com/cygwin/tcp_wrappers_7.6/tcp_wrappers-7.6-1.tar.bz2
Thanks Corinna, I have already started looking at dll'izing the code.
Will be working on it through the weekend on a virtual machine as I
expect I will break things while trying to get it to work ;) I expect I
should be able to have it working with inetd within a month or so
(giving time for
Ok, I was basing my response on the info I got from Charles, where he
pointed out that libwrap declares certain ints as extern, leaving tcpd
and ssh to define them. I am not familiar with DLL's so I am going
solely by what he says, which I expect is accurate considering the work
he has already
On Thu, Jun 27, 2002 at 10:21:20AM -0400, Prentis Brooks wrote:
Ok, I was basing my response on the info I got from Charles, where he
pointed out that libwrap declares certain ints as extern, leaving tcpd
and ssh to define them. I am not familiar with DLL's so I am going
solely by what he
Yeah, my thoughts as well, we really don't want to deviate too far from
the base package. Let me tinker and see how it works, will let you know
what I find :)
On Thu, 27 Jun 2002, Corinna Vinschen wrote:
On Thu, Jun 27, 2002 at 10:21:20AM -0400, Prentis Brooks wrote:
Ok, I was basing my
[Per instructions at http://kde-cygwin.sourceforge.net/kde2.php]
On Thu, Jun 27, 2002 at 08:02:47PM +1000, Robert Collins wrote:
AFAICT http://prdownloads.sf.net/kde-cygwin/setup.ini is not a valid
setup.ini.
It's a redirect page of some sort.
Yes. They've been screwed by the
On Thu, Jun 27, 2002 at 07:49:09PM +0100, Chris January wrote:
If it overwrites it, then I have packaged it wrongly. It should put
ps.exe
and kill.exe into separate subdirectories, i.e. /bin/procps/ps.exe and
/usr/bin/procps/kill.exe.
PLEASE do not differentiate between /bin and
Chris January wrote:
PLEASE do not differentiate between /bin and /usr/bin. This caused no
end of trouble during the early days of setup.exe when setup didn't
*always* follow the mounts. Granted, setup is much better about that
sort of thing now, but don't tempt fate.
There's no need for
PLEASE do not differentiate between /bin and /usr/bin. This caused no
end of trouble during the early days of setup.exe when setup didn't
*always* follow the mounts. Granted, setup is much better about that
sort of thing now, but don't tempt fate.
There's no need for separate /bin and
On Thu, Jun 27, 2002 at 10:38:55PM +0100, Chris January wrote:
Ok. Do you have any thoughts on where I should put ps.exe and kill.exe?
They need to be somewhere other than /bin, but available should the user
wish to use them. Perhaps I could rename them instead? procps.exe and
prockill.exe,
Chris January wrote:
Ok. Do you have any thoughts on where I should put ps.exe and kill.exe?
I ended up renaming 'clear.exe' from the ncurses dist to 'clearn.exe' to
avoid conflicts with the 'clear' package. (In ncurses, 'clear.exe' is
not a 'test' program, so it didn't go into
Ok. Do you have any thoughts on where I should put ps.exe and kill.exe?
I ended up renaming 'clear.exe' from the ncurses dist to 'clearn.exe' to
avoid conflicts with the 'clear' package. (In ncurses, 'clear.exe' is
not a 'test' program, so it didn't go into bin/ncurses-test-*/; it went
I'm in the process of checking in some stuff to the cygwin gcc branch.
I've checked in my most recent set of changes (mainly for -mno-cygwin)
and am currently in the process of checking in the merged changes from
the main 3.1.1 branch. It's taking forever, though.
Anyway, I'm zeroing in on a
Sah-weeet.
--
Gary R. Van Sickle
Brewer. Patriot.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor
Sent: Thursday, June 27, 2002 11:13 PM
To: [EMAIL PROTECTED]
Subject: cygwin gcc 3.1 branch updated
I'm in the process of
26 matches
Mail list logo
