A few months back, I added support for .lzma packages to setup-1.7.exe.
I did this by directly imported a few files from the LZMA SDK, and
writing an interface class.
Now I want to add support for .xz packages. Unfortunately, the xz file
format is a bit more intense, and would require importing
On Sat, Jun 20, 2009 at 03:19:39AM -0400, Charles Wilson wrote:
A few months back, I added support for .lzma packages to setup-1.7.exe.
I did this by directly imported a few files from the LZMA SDK, and
writing an interface class.
You've said what you want to do but you haven't said *why*. What
Christopher Faylor wrote:
You've said what you want to do but you haven't said *why*. What is the
advantage of further complicating a complicated program by adding .xz
support, espcially given the lack of adoption of the lzma format?
Even I haven't adopted the .lzma format for cygwin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Charles Wilson on 6/20/2009 12:00 PM:
Christopher Faylor wrote:
You've said what you want to do but you haven't said *why*. What is the
advantage of further complicating a complicated program by adding .xz
support, espcially given
On Sat, Jun 20, 2009 at 03:11:09PM -0600, Eric Blake wrote:
According to Charles Wilson on 6/20/2009 12:00 PM:
Christopher Faylor wrote:
You've said what you want to do but you haven't said *why*. What is
the advantage of further complicating a complicated program by adding
.xz support, espcially
For both 1.5 and 1.7:
wget http://mintty.googlecode.com/files/mintty-0.4.1-1.tar.bz2
wget http://mintty.googlecode.com/files/mintty-0.4.1-1-src.tar.bz2
Thanks,
Andy
On Sat, Jun 20, 2009 at 05:16:28PM -0400, Christopher Faylor wrote:
On Sat, Jun 20, 2009 at 03:11:09PM -0600, Eric Blake wrote:
According to Charles Wilson on 6/20/2009 12:00 PM:
Christopher Faylor wrote:
You've said what you want to do but you haven't said *why*. What is
the advantage of further
Eric Blake wrote:
Not just that, but automake itself was the one that made distribution in
.lzma possible in the first place, but now automake recommends .xz instead
of .lzma. In other words, with automake 1.11 now out, it is very easy for
upstream packages to use .xz, with its smaller file
Christopher Faylor wrote:
In case it isn't clear, I didn't ask for an explanation just to be mean.
I really did want the rationale to be archived in cygwin-apps.
No offense taken. You were right to ask.
--
Chuck
Ken Brown wrote:
On 6/17/2009 3:17 PM, Jon TURNEY wrote:
+ emacs execbash -l -c /usr/bin/emacs
notepad execnotepad
xload execxload -display %display% # Comment
}
The most important part of this is changing the way emacs is called;
the original version
Frédéric Bron wrote:
If I run rxvt-x (1.5 or 1.7) with Xwin (1.7), when I select something
in the terminal output and then type Ctrl-V in any Windows
application, this does not work. Some application say that the
clipboard is like corrupted. In general, if I type Ctrl-V several
times, after a
On 6/20/2009 4:43 PM, Jon TURNEY wrote:
Ken Brown wrote:
I
prefer bash -l -c /usr/bin/emacs so that the bash initialization
files are processed before emacs starts. For various reasons, I want
the environment inside emacs to be the same as the usual bash
environment. I suspect that most
Ken Brown wrote...
What's the reason for launching everything using sh rather than bash?
If I'm reading the bash documentation correctly, it means that
~/.bash_profile won't get executed (though it would get executed if it
were renamed ~/.profile).
Ken
I've always wondered the same
Den 2009-06-18 21:22 skrev Yaakov (Cygwin/X):
On 18/06/2009 13:31, Peter Rosin wrote:
There is a pending patch for libtool that adds MSVC support. That patch
will not need this, so please special case this to only be active for
gcc (and whatever else needs it).
AFAICS from your patches,
Peter Rosin wrote:
ltwrappers are just replacing the old wrappers AFAIK, and those are
indeed needed by the MSVC patches, so that premise has already changed.
If you can't be bothered to cooperate with those patches then I can
switch to arguing that cccl (wrapper for MSVC) is supported by
The xz package is the successor to lzma. Its command-line tools
support both .lzma files and the new .xz format, and it ships with
compatibility links so you don't even need to retrain your fingers:
'lzma', 'lzcat', etc, are all still present. However, you probably
should: .xz files are already
The xz package is the successor to lzma. Its command-line tools
support both .lzma files and the new .xz format, and it ships with
compatibility links so you don't even need to retrain your fingers:
'lzma', 'lzcat', etc, are all still present. However, you probably
should: .xz files are already
GNU libtool is a generic library support script. Libtool hides the
complexity of using shared libraries behind a consistent, portable
interface.
This is a bugfix update.
[[ compiled using gcc-3.4.4-999 ]]
Unless there are serious issues with this package, it is likely to be
the last version of
GNU libtool is a generic library support script. Libtool hides the
complexity of using shared libraries behind a consistent, portable
interface.
This is a bugfix and feature enhancement update.
[[ compiled using gcc-3.4.4-999 ]]
This release is specific for cygwin-1.7, but it differs from the
Don't know how you fix it but now I am able to use git on cygwin 1.7 and
using cygwin protocol.
So cygwin is as stable as 1.5 for my use.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation:
setup-1.7.exe installs the package 'cygwin-doc', version 1.5-1.
This package includes /usr/share/info/cygwin.info. cygwin.info
references two files, 'cygwin-ug-net.info' and 'cygwin-api.info',
which are not included in 'cygwin-doc':
$ cygcheck -c cygwin-doc
Cygwin Package Information
Package
When I ran setup-1.7.exe with the default set of packages
selected, the following error message was displayed:
running: C:\cygwin-1.7\bin\bash.exe --norc --noprofile -c
/etc/postinstall/base-files-profile.sh
abnormal exit: exit code=-1073741819
'base-files-profile.sh' contains the following
On Sat, Jun 20, 2009 at 01:02:17AM -0400, Charles Wilson wrote:
Christopher Faylor wrote:
On Sat, Jun 20, 2009 at 12:01:41AM -0400, Christopher Faylor wrote:
And, just for the sake of accuracy, there should be fewer unable to
remaps thanks to my 2009-06-07 change.
Yeah -- now I remember
On Sat, Jun 20, 2009 at 01:36:01PM +0200, Vincent R. wrote:
Don't know how you fix it but now I am able to use git on cygwin 1.7 and
using cygwin protocol.
So cygwin is as stable as 1.5 for my use.
Now, *that* one was probably one of Corinna's many changes to networking.
cgf
--
Unsubscribe
On Sat, Jun 20, 2009 at 11:39:59AM -0400, Mark Harig wrote:
When I ran setup-1.7.exe with the default set of packages
selected, the following error message was displayed:
running: C:\cygwin-1.7\bin\bash.exe --norc --noprofile -c
/etc/postinstall/base-files-profile.sh
abnormal exit: exit
The two files 'base-files-mketc.sh' and 'base-files-profiles.sh' included
in the 'base-files' package have their permissions set to 644 while all
other scripts in /etc/postinstall/ have their permissions set to 755.
Is this a side-effect of 'base-files-profiles.sh' not completing without
'dirname' is /usr/bin/dirname. Does setup-1.7.exe set
PATH before running 'base-files-profile.sh'? If not,
then this would account for the error.
It is possible to rewrite the command without using
'dirname':
/bin/mkdir -p ${fDest%/*}
$ cygcheck -f /etc/postinstall/base-files-profile.sh
Christopher Faylor wrote:
Given the fact that I added the previous add data after the dll was
loaded code, which apparently caused its share of remap problems, I
think this particular accomplishment is pretty much a zero.
Doesn't matter. I'm still overjoyed. If it wouldn't get me
After installing all default, base packages in Cygwin,
I attempted to uninstall this base set by clicking on the
cycle button/icon of the 'All' category (while the setup
view for packages was set to 'Category') until 'Uninstall'
was displayed for 'All' and for all sub-categories.
When I clicked
Hi,
Sometimes pipes, created with mknod, seems not to be work fully correct.
Most of the time I can do:
mknod /var/run/CONT p
read -t 2 signal /var/run/CONT.
After 2 seconds I receive a timeout and the read returns.
But sometimes the read will wait forever. And also if I write something
to
On Sat, Jun 20, 2009 at 09:14:08PM +0200, Matthias Meyer wrote:
Sometimes pipes, created with mknod, seems not to be work fully correct.
Most of the time I can do:
mknod /var/run/CONT p
read -t 2 signal /var/run/CONT.
After 2 seconds I receive a timeout and the read returns.
But sometimes the
Den 2009-06-20 09:05 skrev Charles Wilson:
Peter Rosin wrote:
ltwrappers are just replacing the old wrappers AFAIK, and those are
indeed needed by the MSVC patches, so that premise has already changed.
If you can't be bothered to cooperate with those patches then I can
switch to arguing that
After running setup-1.7.exe to install the package 'rxvt',
I found the following error in /var/log/setup.log.full:
2009/06/20 16:00:17 running: C:\cygwin-1.7\bin\bash.exe --norc
--noprofile -c /etc/postinstall/rxvt.sh
Using the default version of /etc/X11/app-defaults/Rxvt
Mark Harig wrote:
Potential app conflicts:
Logitech Process Monitor service
Detected: HKLM Registry Key, Named process.
You definitely need to stop and disable that service. It borks cygwin
something rotten.
cheers,
DaveK
--
Problem reports:
Hi!
I was just wondering about the customs on cygwon-apps.
I have posted an ITP for a package to be included in cygwin which is
in Fedora, but haven't got any feedback yet. Before asking again for a
review I wanted to know what are the general guidelines, customs on
reposting requests for a
Mark Harig wrote:
Is the 'rxvt' package responsible for creating these
missing directories?
Well, *I* think they ought to be created by the X system. Currently,
you kinda get them by default IF you install any of the X-related
packages, because unlike rxvt, those other package directly
Potential app conflicts:
Logitech Process Monitor service
Detected: HKLM Registry Key, Named process.
You definitely need to stop and disable that service. It borks cygwin
something rotten.
Thank you. I will try that (anything to give my cygwin
processes better behavior than they
That having been said...rxvt is stealing a march by assuming
/etc/X11/app-defaults/ exists. It's not clear -- if all the other
packages did it the rxvt way -- WHO exactly should be responsible for
creating the directory.
1. 'rxvt' is advertised as being available without X, so
it
Mark Harig wrote:
Potential app conflicts:
Logitech Process Monitor service
Detected: HKLM Registry Key, Named process.
You definitely need to stop and disable that service. It borks cygwin
something rotten.
Thank you. I will try that (anything to give my cygwin
processes
Mark Harig wrote:
1. stuff
2. more stuff
3. yet more stuff
Sure, all those things would be great, and given the limited time the
few volunteers have to address such things it'd be great to satisfy that
checklist. But if we had to meet some zero-defect six-sigma policy,
cygwin would have about
Dave Korn wrote:
Is this problem with the Logitech Process Monitor service
described in the Cygwin documentation?
http://cygwin.com/faq/faq.using.html#faq.using.bloda
Thanks again for the additional information. I will be working
my way through the entire FAQ at that link.
Federico Hernandez wrote:
Hi!
I was just wondering about the customs on cygwon-apps.
I have posted an ITP for a package to be included in cygwin which is
in Fedora, but haven't got any feedback yet. Before asking again for a
review I wanted to know what are the general guidelines, customs on
The xz package is the successor to lzma. Its command-line tools
support both .lzma files and the new .xz format, and it ships with
compatibility links so you don't even need to retrain your fingers:
'lzma', 'lzcat', etc, are all still present. However, you probably
should: .xz files are already
GNU libtool is a generic library support script. Libtool hides the
complexity of using shared libraries behind a consistent, portable
interface.
This is a bugfix update.
[[ compiled using gcc-3.4.4-999 ]]
Unless there are serious issues with this package, it is likely to be
the last version of
The xz package is the successor to lzma. Its command-line tools
support both .lzma files and the new .xz format, and it ships with
compatibility links so you don't even need to retrain your fingers:
'lzma', 'lzcat', etc, are all still present. However, you probably
should: .xz files are already
GNU libtool is a generic library support script. Libtool hides the
complexity of using shared libraries behind a consistent, portable
interface.
This is a bugfix and feature enhancement update.
[[ compiled using gcc-3.4.4-999 ]]
This release is specific for cygwin-1.7, but it differs from the
46 matches
Mail list logo
