-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| - Creating filenames with special DOS characters '', '*', ':', '',
| '', '|' is supported.
|
| - Creating files with special DOS device filename components (aux,
| nul, prn) is supported.
|
| - File name are case
On Jul 31 01:56, Yaakov (Cygwin Ports) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| - Creating filenames with special DOS characters '', '*', ':', '',
| '', '|' is supported.
|
| - Creating files with special DOS device filename components (aux,
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| setup is a Win32 application. It won't know about this. Thou shalt
| not create packages which rely on case-sensitivity as part of the
| net distro.
That's what I thought. So while managed mounts will no longer be
On Jul 31 03:28, Yaakov (Cygwin Ports) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| setup is a Win32 application. It won't know about this. Thou shalt
| not create packages which rely on case-sensitivity as part of the
| net distro.
That's what I
Corinna Vinschen wrote:
Illegal? The only illegal chars are slash and backslash, even on
case-insensitive mounts. Does it really occur often that you have two
filenames in the same dir only differing by case?
I'd imagine aux and prn are still illegal, right? The numbers are
fewer, these
On Jul 31 08:59, Charles Wilson wrote:
Corinna Vinschen wrote:
Illegal? The only illegal chars are slash and backslash, even on
case-insensitive mounts. Does it really occur often that you have two
filenames in the same dir only differing by case?
I'd imagine aux and prn are still
On Jul 31 15:23, Corinna Vinschen wrote:
On Jul 31 08:59, Charles Wilson wrote:
Corinna Vinschen wrote:
Illegal? The only illegal chars are slash and backslash, even on
case-insensitive mounts. Does it really occur often that you have two
filenames in the same dir only differing by
On Jul 31 15:30, Corinna Vinschen wrote:
On Jul 31 15:23, Corinna Vinschen wrote:
On Jul 31 08:59, Charles Wilson wrote:
Corinna Vinschen wrote:
Illegal? The only illegal chars are slash and backslash, even on
case-insensitive mounts. Does it really occur often that you have two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Illegal? The only illegal chars are slash and backslash, even on
| case-insensitive mounts. Does it really occur often that you have two
| filenames in the same dir only differing by case?
For Cygwin I understand that,
On Jul 31 10:05, Yaakov (Cygwin Ports) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Illegal? The only illegal chars are slash and backslash, even on
| case-insensitive mounts. Does it really occur often that you have two
| filenames in the same dir only
On Jul 31 16:10, Corinna Vinschen wrote:
On Jul 31 15:30, Corinna Vinschen wrote:
What still won't work, though is to start an application called, for
instance, aux.exe. The reason is that the CreateProcess call in
spawn/exec is still a Win32 call which will treat this filename as a
DOS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 7/28/2008 9:27 AM:
| # check the window size after each command and, if necessary,
| # update the values of LINES and COLUMNS.
| shopt -s checkwinsize
|
| would it work in cygwin? Also;
|
| Looks like bash on Cygwin
On Tue, July 29, 2008 12:37 pm, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 7/28/2008 9:27 AM:
| # check the window size after each command and, if necessary,
| # update the values of LINES and COLUMNS.
| shopt -s checkwinsize
|
| would
On Tue, July 22, 2008 6:42 pm, Corinna Vinschen wrote:
You can now call mkpasswd and mkgroup without any -l or -d parameter
and both tools choose by themselves what information to print, depending
on the machine being a domain member machine or not.
This should result in a matching
On Jul 28 15:51, John Morrison wrote:
On Tue, July 22, 2008 6:42 pm, Corinna Vinschen wrote:
You can now call mkpasswd and mkgroup without any -l or -d parameter
and both tools choose by themselves what information to print, depending
on the machine being a domain member machine or
On Mon, Jul 28, 2008 at 05:27:50PM +0200, Corinna Vinschen wrote:
On Jul 28 15:51, John Morrison wrote:
On Tue, July 22, 2008 6:42 pm, Corinna Vinschen wrote:
You can now call mkpasswd and mkgroup without any -l or -d parameter
and both tools choose by themselves what information to
I just uploaded 1.7.0-21. It contains the following important changes:
- Fix for the fix for the problem with native Win32 apps described in this
thread: http://cygwin.com/ml/cygwin/2008-07/msg00457.html
My first solution didn't work for applications started from a remote
share path
I'd be happy if even the most important packages have been rebuilt for
1.7. So far the reactions from the package maintainers were somewhat
reticent.
I think that'll probably alter once there's a setup for 1.7.
Ditto here. Waiting for setup for 1.7, then I'll rebuild all of my
On Jul 23 21:44, John Morrison wrote:
On Wed, July 23, 2008 7:00 pm, Corinna Vinschen wrote:
I'd be happy if even the most important packages have been rebuilt for
1.7. So far the reactions from the package maintainers were somewhat
reticent.
I think that'll probably alter once there's
On Thu, July 24, 2008 10:08 am, Corinna Vinschen wrote:
On Jul 23 21:44, John Morrison wrote:
On Wed, July 23, 2008 7:00 pm, Corinna Vinschen wrote:
I'd be happy if even the most important packages have been rebuilt for
1.7. So far the reactions from the package maintainers were somewhat
On Jul 23 22:44, Yaakov (Cygwin Ports) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| I'd be happy if even the most important packages have been rebuilt for
| 1.7. So far the reactions from the package maintainers were somewhat
| reticent.
I know I've
On Jul 24 10:17, John Morrison wrote:
On Thu, July 24, 2008 10:08 am, Corinna Vinschen wrote:
Please with sugar?
I only have windows at work now and all my time is 'allocated' to
projects... trying! If I don't get it done before the weekend I'll get a
virtual machine running. Promise.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Honestly, I don't know. Maybe it isn't. But so far I'm still thinking
| that a parallel 1.7 install should only be a temporary solution for
| developers and maintainers. It's not something I would like to drag
| on for
On Jul 24 11:17, Yaakov (Cygwin Ports) wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Honestly, I don't know. Maybe it isn't. But so far I'm still thinking
| that a parallel 1.7 install should only be a temporary solution for
| developers and maintainers.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| When 1.7 goes gold, the idea is to install over an 1.5 install. Or not.
| It's the choice of the user. Installing over 1.5 is supported by the
| base-cygwin package, which is supposed to convert the registry mount
|
On Jul 23 12:25, Yaakov (Cygwin Ports) wrote:
Corinna Vinschen wrote:
| When 1.7 goes gold, the idea is to install over an 1.5 install. Or not.
| It's the choice of the user.
The advantage of starting fresh with 1.7 would allow us to dump a lot
of obsolete packages from the distro [...]
On Jul 21 18:42, Yaakov (Cygwin Ports) wrote:
I've considered making the switch, as the new features in 1.7 (namely
IPv6 and wchar functions) would make porting *much* easier. It might
also provide the chance to finally close the gap between Ports and the
distro, and generally improve our
I just uploaded 1.7.0-20. It contains the following important changes:
- Fix for the problem with native Win32 apps described in this thread:
http://cygwin.com/ml/cygwin/2008-07/msg00457.html
- Reworked mkpasswd and mkgroup tools including the documentation.
The usage changed and you have
On Jul 18 14:09, Corinna Vinschen wrote:
On Jul 17 18:18, Eric Blake wrote:
Somewhere between setting obcaseinsensitive to 0 yesterday and
upgrading
to the new cygwin1.dll today, I'm now suffering from an inability to
modify files on a shared drive on my work machine. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| again I would like to encourage the Cygwin maintainers, to try the new
| Cygwin 1.7.0 release and to look for problems in their packages which
| might be a result of the fairly massive changes in Cygwin 1.7. I
| attached
--- Corinna Vinschen ha scritto:
On Jul 18 13:56, Christopher Faylor wrote:
On Fri, Jul 18, 2008 at 07:10:10PM +0200, Corinna
Vinschen wrote:
On Jul 18 18:36, Marco Atzeri wrote:
Is it still unable to handle empty tarball ?
... of a certain type, yes, unfortunately.
Fortunately
On Jul 18 15:28, Bill Hoffman wrote:
Corinna Vinschen wrote:
Download a 1.7 distro using http://cygwin.com/setup-1.7.exe
Cygwin 1.7 and 1.5 can run in parallel sessions on the same machine, but
the installation in parallel needs some manual intervention. Setup.exe
is not yet using the new
On Jul 17 17:55, Corinna Vinschen wrote:
Hi,
again I would like to encourage the Cygwin maintainers, to try the new
Cygwin 1.7.0 release and to look for problems in their packages which
might be a result of the fairly massive changes in Cygwin 1.7. I
attached a list of the changes below.
On Jul 17 18:18, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 7/17/2008 9:55 AM:
| Hi,
|
| again I would like to encourage the Cygwin maintainers, to try the new
| Cygwin 1.7.0 release and to look for problems in their packages which
|
On Jul 18 09:34, Corinna Vinschen wrote:
On Jul 17 18:18, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 7/17/2008 9:55 AM:
| Hi,
|
| again I would like to encourage the Cygwin maintainers, to try the new
| Cygwin 1.7.0 release and
On Jul 18 09:54, Corinna Vinschen wrote:
On Jul 18 09:34, Corinna Vinschen wrote:
On Jul 17 18:18, Eric Blake wrote:
Somewhere between setting obcaseinsensitive to 0 yesterday and upgrading
to the new cygwin1.dll today, I'm now suffering from an inability to
modify files on a shared
On Jul 18 10:09, Corinna Vinschen wrote:
On Jul 18 09:54, Corinna Vinschen wrote:
On Jul 18 09:34, Corinna Vinschen wrote:
On Jul 17 18:18, Eric Blake wrote:
Somewhere between setting obcaseinsensitive to 0 yesterday and upgrading
to the new cygwin1.dll today, I'm now suffering from
--- Corinna Vinschen ha scritto:
Hi,
Hi Corinna,
Download a 1.7 distro using
http://cygwin.com/setup-1.7.exe
Is it still unable to handle empty tarball ?
Bye
Marco
Posta, news, sport, oroscopo: tutto in una sola pagina.
Crea l#39;home page che piace a te!
On Jul 18 18:36, Marco Atzeri wrote:
--- Corinna Vinschen ha scritto:
Download a 1.7 distro using
http://cygwin.com/setup-1.7.exe
Is it still unable to handle empty tarball ?
... of a certain type, yes, unfortunately. Fortunately it doesn't
stop the whole setup process, it just prints
On Fri, Jul 18, 2008 at 07:10:10PM +0200, Corinna Vinschen wrote:
On Jul 18 18:36, Marco Atzeri wrote:
--- Corinna Vinschen ha scritto:
Download a 1.7 distro using
http://cygwin.com/setup-1.7.exe
Is it still unable to handle empty tarball ?
... of a certain type, yes, unfortunately.
On Jul 18 13:56, Christopher Faylor wrote:
On Fri, Jul 18, 2008 at 07:10:10PM +0200, Corinna Vinschen wrote:
On Jul 18 18:36, Marco Atzeri wrote:
Is it still unable to handle empty tarball ?
... of a certain type, yes, unfortunately. Fortunately it doesn't
stop the whole setup process, it
Corinna Vinschen wrote:
Download a 1.7 distro using http://cygwin.com/setup-1.7.exe
Cygwin 1.7 and 1.5 can run in parallel sessions on the same machine, but
the installation in parallel needs some manual intervention. Setup.exe
is not yet using the new registry location and will happily
Corinna Vinschen wrote:
Actually I don't think it can handle any type of empty tarball can it?
I don't know. I thought it handles one type and complains about the
other. I didn't actually test it.
It can handle the type created by bzip2 /dev/null but not the tar -T
/dev/null type. I
Hi,
again I would like to encourage the Cygwin maintainers, to try the new
Cygwin 1.7.0 release and to look for problems in their packages which
might be a result of the fairly massive changes in Cygwin 1.7. I
attached a list of the changes below. The latest changes are:
- Changes in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 7/17/2008 9:55 AM:
| Hi,
|
| again I would like to encourage the Cygwin maintainers, to try the new
| Cygwin 1.7.0 release and to look for problems in their packages which
| might be a result of the fairly massive
45 matches
Mail list logo
