Yaakov Selkowitz writes:
On 2014-11-10 12:31, Achim Gratz wrote:
The current beta packages contain a . in the release number. That dot is
chopped off along with the anything that follows in some places during
install in setup.exe.
Which places exactly? We could just fix this in setup
Corinna Vinschen writes:
This only happens in genini AFAIK, not in upset. But the dependency
issues might really be related to the test release version numbers.
Yaakov is digging into upset ATM.
OK, when I find time I'll have a look of how to fix it. BTW, is there a
good reason to keep this
On 11/11/2014 17:20, Achim Gratz wrote:
Corinna Vinschen writes:
This only happens in genini AFAIK, not in upset. But the dependency
issues might really be related to the test release version numbers.
Yaakov is digging into upset ATM.
OK, when I find time I'll have a look of how to fix it.
Jon TURNEY writes:
You might want to start by taking a look at
https://cygwin.com/ml/cygwin-apps/2007-02/msg00060.html
If you were worried, I'm not gonna try Perl version objects on
these... :-)
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD
I have some elementary questions regarding the cygwin setup program. I ran the
latest version 2.852 (64 bit).
the options are install / re-install / un-install / default
my understanding is as follows;
choosing install creates a new installation of the selected cygwin components
choosing
On 11/11/2014 7:40 AM, Andrey Repin wrote:
Greetings, Yaakov Selkowitz!
In short, elusive benefits of having a separate cygwin-specific clean homes
versus confusing disjoint of multiple places to look for single user's files,
settings, and other stuff when it comes to backups and migrating
2014-11-11 1:45 GMT+01:00 Andrey Repin:
I see literally zero reason to maintain separate, cygwin-specific home
directory.
I think I have to disagree with you. When mixing MSYS, msysGit and
Cygwin in the same home directory the dot-files can become a problem.
Especially when it comes to line
On Nov 10 23:19, Warren Young wrote:
On Nov 10, 2014, at 6:38 PM, Jeffrey Altman jalt...@secure-endpoints.com
wrote:
My personal preference would be for the Cygwin Home directory to be
created under
%HOMEPATH%\AppData\Roaming\Cygwin
That’s certainly the way you’re *supposed* to do
On Nov 10 20:38, Jeffrey Altman wrote:
On 11/10/2014 3:52 PM, Corinna Vinschen wrote:
Hi,
after a long discussion in RL today, I came to the conclusion that
there's a major problem in the current handling of the user's home
directory in AD environments in the new user account code
Marco Atzeri wrote:
On 11/11/2014 7:40 AM, Andrey Repin wrote:
In short, elusive benefits of having a separate cygwin-specific clean
homes
versus confusing disjoint of multiple places to look for single user's
files,
settings, and other stuff when it comes to backups and
On Nov 10 23:09, Warren Young wrote:
On Nov 10, 2014, at 1:52 PM, Corinna Vinschen corinna-cyg...@cygwin.com
wrote:
Shall the db entries utilize the Windows home folder if it exits(*)
and drop using the unixHomeDirectory? It seems inevitable…
Use of AD implies some level of security
Corinna Vinschen corinna-cygwin at cygwin.com writes:
One possible, but not naturally useful default behaviour is what
the current code does:
1. Utilize the unixHomeDirectory AD attribute.
2. If unixHomeDirectory is empty, fall back to /home/$USER.
[...]
Default to /home/$USER unless a
On Nov 11 11:18, Corinna Vinschen wrote:
On Nov 10 23:09, Warren Young wrote:
On Nov 10, 2014, at 1:52 PM, Corinna Vinschen corinna-cyg...@cygwin.com
wrote:
Shall the db entries utilize the Windows home folder if it exits(*)
and drop using the unixHomeDirectory? It seems
On Nov 11 11:05, Achim Gratz wrote:
Corinna Vinschen corinna-cygwin at cygwin.com writes:
One possible, but not naturally useful default behaviour is what
the current code does:
1. Utilize the unixHomeDirectory AD attribute.
2. If unixHomeDirectory is empty, fall back to /home/$USER.
On Nov 11 07:39, Christian Franke wrote:
Corinna Vinschen wrote:
On Nov 10 20:21, Christian Franke wrote:
What will be the behavior of the predecessor of e.g. the csih function
csih_create_unprivileged_user if called with USER without HOST prefix,
machine is inside of domain and the user does
On Nov 10 22:33, Yaakov Selkowitz wrote:
On 2014-11-10 22:23, Yaakov Selkowitz wrote:
Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode
libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash
libncursesw10
[snip]
Now that I think about it, regardless of libgcc1,
Good evening:
I recently ran the latest setup-x86.exe to pick up the recent updates for my
Windows XP (SP3) system. I received the following error message.
Package: libgvc6
libgvc6.sh exit code 134
From what I can tell, this means the installation process received a
SIGABORT signal during
One big vote for the '/etc/nsswitch.conf' idea. I think the truth of
the matter is that enterprise environments are way too dynamic (and
inconsistent) to attempt to satisfy the majority of configurations
with any particular default ordering assumption.
Another user brought up a good point about
On Nov 11 07:11, Bryan Berns wrote:
One big vote for the '/etc/nsswitch.conf' idea. I think the truth of
the matter is that enterprise environments are way too dynamic (and
inconsistent) to attempt to satisfy the majority of configurations
with any particular default ordering assumption.
Another:
1. Add a setting to /etc/nsswitch.conf which allows to specify one of
the above:
home: [unix|win|home]...
- unix means, set pw_dir to unixHomeDirectory
- win means, set pw_dir to homeDirectory
- home means, set pw_dir to /home/$USER
- Multiple entries are
On 11/11/2014 4:59 AM, Corinna Vinschen wrote:
Please keep in mind that I'm talking about the Cygwin home dir not as
a default value which can be overridden in /etc/passwd, but of a Cygwin
home dir as returned by Cygwin when fetching the passwd entry from AD,
and no passwd file exists. This
On 11/11/2014 6:53 AM, Corinna Vinschen wrote:
On Nov 10 22:33, Yaakov Selkowitz wrote:
On 2014-11-10 22:23, Yaakov Selkowitz wrote:
Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode
libstdc++6 terminfo sed gzip libpcre1 grep libreadline7 bash
libncursesw10
[snip]
Now that
On 11/11/2014 9:14 AM, Ken Brown wrote:
On 11/11/2014 6:53 AM, Corinna Vinschen wrote:
On Nov 10 22:33, Yaakov Selkowitz wrote:
On 2014-11-10 22:23, Yaakov Selkowitz wrote:
Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode
libstdc++6 terminfo sed gzip libpcre1 grep
Greetings, Frank Fesevur!
I see literally zero reason to maintain separate, cygwin-specific home
directory.
I think I have to disagree with you. When mixing MSYS, msysGit and
Cygwin in the same home directory the dot-files can become a problem.
Especially when it comes to line ending in
Greetings, Corinna Vinschen!
Shall the db entries utilize the Windows home folder if it exits(*)
and drop using the unixHomeDirectory? It seems inevitable…
Use of AD implies some level of security consciousness. The ability to
write to c:\cygwin — not just during installation, but
On Nov 11 10:02, Ken Brown wrote:
On 11/11/2014 9:14 AM, Ken Brown wrote:
On 11/11/2014 6:53 AM, Corinna Vinschen wrote:
On Nov 10 22:33, Yaakov Selkowitz wrote:
On 2014-11-10 22:23, Yaakov Selkowitz wrote:
Dependency order of packages: libgcc1 base-cygwin cygwin dash tzcode
libstdc++6
From: Achim Gratz
Nellis, Kenneth writes:
Jeremy's solution is closest to what I was looking for; however I need
it to work from a networked, non-drive-mapped folder.
(CMD.EXE doesn't like UNC paths.) I hadn't realized that I could pipe
a script into bash.
The solution to the UNC
On Nov 11 08:51, Jeffrey Altman wrote:
On 11/11/2014 4:59 AM, Corinna Vinschen wrote:
Please keep in mind that I'm talking about the Cygwin home dir not as
a default value which can be overridden in /etc/passwd, but of a Cygwin
home dir as returned by Cygwin when fetching the passwd entry
Corinna Vinschen writes:
Looks good, but maybe allow the AD attribute to be explicitly named (e.g.
cygwinHomeDirectory).
Cygwin schema extension? :)
I don't see why not, given that there's the possibility of having
different information for Windows, Cygwin and UNIX in the same AD. But
more
On Nov 11 17:44, Achim Gratz wrote:
Corinna Vinschen writes:
Looks good, but maybe allow the AD attribute to be explicitly named (e.g.
cygwinHomeDirectory).
Cygwin schema extension? :)
I don't see why not, given that there's the possibility of having
different information for Windows,
On Nov 11 18:29, Andrey Repin wrote:
Greetings, Corinna Vinschen!
Shall the db entries utilize the Windows home folder if it exits(*)
and drop using the unixHomeDirectory? It seems inevitable…
Use of AD implies some level of security consciousness. The ability to
write to
Corinna Vinschen writes:
On Nov 11 10:02, Ken Brown wrote:
Of course, this still doesn't solve the problem of making sure that the
_autorebase postinstall script runs whenever the user installs a package
containing DLLs. I wonder if we should reconsider Achim's proposal. If I
understand
I am trying to port a cygwin application that uses cron from a WinXP PC to a
Win7 Pro PC and I find some cron jobs won't run. Specifically, I need to run
an Excel program from a cron job and this doesn't work on my Win7 PC.
In order to run an Excel program from cygwin I have this run.excel
On Nov 11 18:08, Achim Gratz wrote:
Corinna Vinschen writes:
On Nov 11 10:02, Ken Brown wrote:
Of course, this still doesn't solve the problem of making sure that the
_autorebase postinstall script runs whenever the user installs a package
containing DLLs. I wonder if we should
Corinna Vinschen writes:
I understand that you're patching setup to recognize the autorebase
package by name, but how does it recognize other perpetual postinstall
scripts ATM?
I actually match an _always suffix before the file extension. So once
such a file gets installed in
Hello, I noticed there was an update to libssh uploaded yesterday (11/10/14):
https://cygwin.com/packages/x86/libssh2_1/
I don't see anything about an update to this in the announcements section.
I also tried searching the site and can't find anything about an update to
libssh.
Can someone
Greetings, Kertz, Denis (D)** CTR **!
I am trying to port a cygwin application that uses cron from a WinXP PC to
a Win7 Pro PC and I find some cron jobs won't run. Specifically, I need to
run an Excel program from a cron job and this doesn't work on my Win7 PC.
In order to run an Excel
Greetings, Nellis, Kenneth!
From: Achim Gratz
Nellis, Kenneth writes:
Jeremy's solution is closest to what I was looking for; however I need
it to work from a networked, non-drive-mapped folder.
(CMD.EXE doesn't like UNC paths.) I hadn't realized that I could pipe
a script into bash.
Hi
Files from /usr/doc/html/docbook-utils-0.6.14/ should probably be
installed into /usr/share/doc/html/docbook-utils
Ciao
Volker
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Hi
Files from /usr/doc/sitecopy should be installed under
/usr/share/doc/sitecopy
Ciao
Volker
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
Greetings, Corinna Vinschen!
Shall the db entries utilize the Windows home folder if it exits(*)
and drop using the unixHomeDirectory? It seems inevitable…
Use of AD implies some level of security consciousness. The ability to
write to c:\cygwin — not just during installation, but
Hi
Older gnutls versions compiled fine with cygwin. Latest versions come
with their own libopts source tree, which is newer than the latest
cygwin version. I get the following error when trying to compile gnutls-3.2.20
In file included from srptool-args.c:43:0:
srptool-args.h:61:3: error: #error
On 2014-11-11 14:44, Dr. Volker Zell wrote:
Older gnutls versions compiled fine with cygwin. Latest versions come
with their own libopts source tree, which is newer than the latest
cygwin version. I get the following error when trying to compile gnutls-3.2.20
In file included from
This is discussed in the texlive release announcement
https://cygwin.com/ml/cygwin-announce/2014-07/msg0.html
under the heading Fontconfig. See also
https://cygwin.com/ml/cygwin-xfree/2014-05/msg00020.html
Yaakov, could we get a fontconfig update that fixes this?
Thanks.
Ken
On 11/11/2014 4:31 PM, phil rosenberg wrote:
This is discussed in the texlive release announcement
https://cygwin.com/ml/cygwin-announce/2014-07/msg0.html
under the heading Fontconfig. See also
https://cygwin.com/ml/cygwin-xfree/2014-05/msg00020.html
Yaakov, could we get a
On 11/11/2014 12:08 PM, Achim Gratz wrote:
Corinna Vinschen writes:
On Nov 11 10:02, Ken Brown wrote:
Of course, this still doesn't solve the problem of making sure that the
_autorebase postinstall script runs whenever the user installs a package
containing DLLs. I wonder if we should
Hello everyone,
I'm just curious, has there been any special focus on performance
improvements in the 64-bit version compared to 32-bit?
I'm asking because I recently upgraded from 32-bit to 64-bit Cygwin, and I
noticed that my bash prompt would show up noticeably quicker when I opened a
new
The following packages have been updated in the Cygwin distribution:
* autogen-5.18.4-1
* libopts25-5.18.4-1
* libopts-devel-5.18.4-1
AutoGen is a tool designed to simplify the creation and maintenance of
programs that contain large amounts of repetitious text. It is
especially valuable in
The following packages have been updated in the Cygwin distribution:
* libssh2_1-1.4.3-1
* libssh2-devel-1.4.3-1
libssh2 is a library implementing the SSH2 protocol.
This release is an update to the latest upstream release.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
On 11/12/2014 3:28 AM, t s wrote:
I have some elementary questions regarding the cygwin setup program. I ran the
latest version 2.852 (64 bit).
wrong mailing list.
Use main one for these questions
the options are install / re-install / un-install / default
my understanding is as follows;
The following packages have been updated in the Cygwin distribution:
* autogen-5.18.4-1
* libopts25-5.18.4-1
* libopts-devel-5.18.4-1
AutoGen is a tool designed to simplify the creation and maintenance of
programs that contain large amounts of repetitious text. It is
especially valuable in
The following packages have been updated in the Cygwin distribution:
* libssh2_1-1.4.3-1
* libssh2-devel-1.4.3-1
libssh2 is a library implementing the SSH2 protocol.
This release is an update to the latest upstream release.
--
Yaakov
52 matches
Mail list logo
