Reini Urban wrote:
Gerrit P. Haase schrieb:
Reini Urban wrote:
Vlad schrieb:
My plan is to use as much shared libraries ( libgd ,
libfreetype ) as practical, and link the missing libraries
statically.
Do you want libming also? (SWF output)
I have a package ready, but not yet
Does anybody has an SQLite package ready for review?
Gerrit
--
=^..^=
On Aug 16 10:20, Chris Sutcliffe wrote:
Included below is my proposal to address the stripping of the w32api
and mingw-runtime after running it by the mingw developers. Is the
proposed solution acceptable?
Are you asking us? I think this is up to you and the mingw team since
your are the one
On Aug 14 12:58, Corinna Vinschen wrote:
I've just uploaded flac, libogg and libvorbis. These three packages
are creating the new Audio category.
So, maintainers of esound and audiofile, would you mind to change your
setup.hint files to add the packages to this new category?
Yaakov? Any
Corinna Vinschen wrote:
On Aug 14 12:58, Corinna Vinschen wrote:
I've just uploaded flac, libogg and libvorbis. These three packages
are creating the new Audio category.
So, maintainers of esound and audiofile, would you mind to change your
setup.hint files to add the packages to this new
On Aug 17 12:47, Gerrit P. Haase wrote:
Corinna Vinschen wrote:
On Aug 14 12:58, Corinna Vinschen wrote:
I've just uploaded flac, libogg and libvorbis. These three packages
are creating the new Audio category.
So, maintainers of esound and audiofile, would you mind to change your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
diffstat: new upstream release
tar: new maintainer, new upstream release. Instead of linking against
binmode.o and forcing text mode on the exceptions even on binary mounts, I
fixed the source code to always request bin mode on the files where it
On Wed, Aug 17, 2005 at 06:24:50AM -0600, Eric Blake wrote:
tar: new maintainer, new upstream release. Instead of linking against
binmode.o and forcing text mode on the exceptions even on binary mounts,
I'm not sure what the above is implying but I didn't link with binmode.o
when I packaged tar.
Singular goes to /opt/Singular
Is this choose of directory valid?
Homepage : http://www.singular.uni-kl.de
License : GPL
Package URLs are below.
Sincerely,
Oliver Wienand
ftp://www.mathematik.uni-kl.de/pub/Math/Singular/devel/WIN/cygwin/release/singular-base/setup.hint
On Aug 17 10:56, Christopher Faylor wrote:
On Wed, Aug 17, 2005 at 06:24:50AM -0600, Eric Blake wrote:
tar: new maintainer, new upstream release. Instead of linking against
binmode.o and forcing text mode on the exceptions even on binary mounts,
I'm not sure what the above is implying but I
On Wed, Aug 17, 2005 at 05:04:32PM +0200, Corinna Vinschen wrote:
On Aug 17 10:56, Christopher Faylor wrote:
On Wed, Aug 17, 2005 at 06:24:50AM -0600, Eric Blake wrote:
tar: new maintainer, new upstream release. Instead of linking against
binmode.o and forcing text mode on the exceptions even
On Wed, Aug 17, 2005 at 04:57:35PM +0200, Oliver Wienand wrote:
Singular goes to /opt/Singular
Is this choose of directory valid?
No.
cgf
I wonder what is wrong that I still got no response...
VH
On Mon, 15 Aug 2005, Vaclav Haisman wrote:
Hi,
I have made Cygwin package of Boost 1.33.0 libraries and I want to propose it
to be included into Cygwin.
I have partitioned it into tree packages: boost-1.33.0-1 libboost-1.33.0-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isn't GNU typist a rather short and redundant sdesc?
I suggest universal typing tutor as from first line of
http://www.gnu.org/software/gtypist/gtypist.html
Or anything else, but please not a description that only repeats the
package name ;-)
PS1:
On Aug 17 11:37, Christopher Faylor wrote:
On Wed, Aug 17, 2005 at 05:04:32PM +0200, Corinna Vinschen wrote:
Am I missing something or shouldn't tar be one of those applications
which should recreate *exactly* what they got? In other words, shouldn't
using binmode under all circumstances,
On Wed, Aug 17, 2005 at 05:40:37PM +0200, Lapo Luchini wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isn't GNU typist a rather short and redundant sdesc?
I suggest universal typing tutor as from first line of
http://www.gnu.org/software/gtypist/gtypist.html
Or anything else, but please not
Christopher Faylor wrote:
On Wed, Aug 17, 2005 at 04:57:35PM +0200, Oliver Wienand wrote:
Singular goes to /opt/Singular
Is this choose of directory valid?
No.
Hmmm, what is wrong with /opt?
Gerrit
--
=^..^=
On Aug 17 17:38, Vaclav Haisman wrote:
I wonder what is wrong that I still got no response...
Well, along the lines of recent discussions, your sdesc and ldesc fields
in the various setup.hint files are somewhat useless. Could you please
change them so that they say something about what boost
On Aug 17 10:56, Christopher Faylor wrote:
On Wed, Aug 17, 2005 at 06:24:50AM -0600, Eric Blake wrote:
tar: new maintainer, new upstream release. Instead of linking against
binmode.o and forcing text mode on the exceptions even on binary mounts,
I'm not sure what the above is implying
On Wed, 17 Aug 2005, Eric Blake wrote:
[snip]
Then you went through the sources, and for all files that manipulate
human-readable files (such as file name lists, as opposed to actual
tars), you added FOPEN_TEXT_READ, defined as rt, to fopen calls,
and O_TEXT to open calls. All file
On Wed, Aug 17, 2005 at 04:10:36PM +, Eric Blake wrote:
On Aug 17 10:56, Christopher Faylor wrote:
On Wed, Aug 17, 2005 at 06:24:50AM -0600, Eric Blake wrote:
tar: new maintainer, new upstream release. Instead of linking against
binmode.o and forcing text mode on the exceptions even on
On Wed, Aug 17, 2005 at 12:22:50PM -0400, Igor Pechtchanski wrote:
On Wed, 17 Aug 2005, Eric Blake wrote:
[snip]
Then you went through the sources, and for all files that manipulate
human-readable files (such as file name lists, as opposed to actual
tars), you added FOPEN_TEXT_READ, defined
Corinna Vinschen wrote:
So, well, what *is* boost? Is it packed with some Linux distro by default?
Which one?
It is one of the packages which must be compilable before a new version
of gcc is released: http://gcc.gnu.org/gcc-3.4/criteria.html
I bet it is available for nearly every Linux
On Wed, 17 Aug 2005, Christopher Faylor wrote:
On Wed, Aug 17, 2005 at 12:22:50PM -0400, Igor Pechtchanski wrote:
On Wed, 17 Aug 2005, Eric Blake wrote:
[snip]
Then you went through the sources, and for all files that manipulate
human-readable files (such as file name lists, as opposed
I'm not sure this is correct. fopen(..., rt) should create LF endings
on binary mounts and CRLF on text mounts... IIUC, the open mode is a hint
to the underlying filesystem whether line ending translation should be
done -- the actual translation is done based on the mount type.
Opening
On Wed, 17 Aug 2005, Eric Blake wrote:
I'm not sure this is correct. fopen(..., rt) should create LF endings
on binary mounts and CRLF on text mounts... IIUC, the open mode is a hint
to the underlying filesystem whether line ending translation should be
done -- the actual translation is
On Wed, Aug 17, 2005 at 12:42:31PM -0400, Igor Pechtchanski wrote:
On Wed, 17 Aug 2005, Christopher Faylor wrote:
On Wed, Aug 17, 2005 at 12:22:50PM -0400, Igor Pechtchanski wrote:
On Wed, 17 Aug 2005, Eric Blake wrote:
[snip]
Then you went through the sources, and for all files that
On Wed, Aug 17, 2005 at 04:47:19PM +, Eric Blake wrote:
I'm not sure this is correct. fopen(..., rt) should create LF
endings on binary mounts and CRLF on text mounts... IIUC, the open
mode is a hint to the underlying filesystem whether line ending
translation should be done -- the actual
On Wed, Aug 17, 2005 at 12:56:54PM -0400, Igor Pechtchanski wrote:
The fact that there are no standards for O_TEXT or rt/wt didn't help
my confusion any.
Well, I guess just relying on the common sense philosophy of I told
it do do this, so that's what I'd expect it to do is something that
can't
On Wed, 17 Aug 2005, Corinna Vinschen wrote:
On Aug 17 17:38, Vaclav Haisman wrote:
I wonder what is wrong that I still got no response...
Well, along the lines of recent discussions, your sdesc and ldesc fields
in the various setup.hint files are somewhat useless. Could you please
You're saying that the programmer can go out of his way to specify the line
ending style that they want but cygwin should allow the mount mode to override
that? I don't agree that this is logical behavior.
Here's my attempt to clarify my understanding of the current
behavior. Tell me if any
On Wed, Aug 17, 2005 at 05:40:45PM +, Eric Blake wrote:
setmode(fd, O_BINARY or O_TEXT) - returns 0 on success, -1 on failure
(different from the cygwin web page doc of returning the previous mode),
and forces mode change. Not a good idea to call it on a tty. Non-POSIX
extension.
No.
But opening with rt is non-POSIX,
I don't see what that has to do with anything.
It means that you have to use #ifdef __CYGWIN__ in your
sources before using it. Some upstream maintainers are
reluctant to add patches with #ifdef code if an alternative
solution can be found that works on
On Wed, 17 Aug 2005, Christopher Faylor wrote:
On Wed, Aug 17, 2005 at 12:56:54PM -0400, Igor Pechtchanski wrote:
The fact that there are no standards for O_TEXT or rt/wt didn't
help my confusion any.
Well, I guess just relying on the common sense philosophy of I told
it do do this, so
On Wed, Aug 17, 2005 at 06:03:58PM +, Eric Blake wrote:
But opening with rt is non-POSIX,
I don't see what that has to do with anything.
It means that you have to use #ifdef __CYGWIN__ in your sources before
using it.
Strangely enough, I now realize that I linked with binmode.o to minimize
i.e., as I said, it sounds like you changed the behavior. If you want
to fix the incremental files so that they are always created with \n
endings that would be great. Otherwise, please don't use the underlying
mount option *for anything*.
Underlying mount points for reading are harmless
Original Message
From: Christopher Faylor
Sent: 17 August 2005 18:20
Let's apply some common sense here, too. You specify wt, what would
you expect? You'd expect a file with CRLF endings, i.e., LF should be
translated to CRLF.
Well, not on a linux box I wouldn't.
If I open a
Making the code work less well because it would be easier for someone to
accept source code is completely backwards from the end user experience
that cygwin is trying to provide. We're not going to sacrifice
*functionality* just to adhere to posix standards.
If the upstream maintainer
Updated setup.hints as promised:
setup.hint:
# Boost 1.33.0 Cygwin package setup.hint
sdesc: Boost 1.33.0 main package
ldesc: Boost provides free peer-reviewed portable C++ source libraries.
The emphasis is on libraries that work well with the C++ Standard
Library. Boost libraries are intended
Yep. I knew that this would be coming from some direction and it is a
wonderful illustration of why I quoted the term common sense.
On Wed, Aug 17, 2005 at 07:22:42PM +0100, Dave Korn wrote:
From: Christopher Faylor
Sent: 17 August 2005 18:20
Let's apply some common sense here, too. You
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christopher Faylor wrote:
I agree. I think Brian sent out a list of packages a while ago
which fell into the nondescriptive sdesc category. It's a shame
that this hasn't been fixed.
It appears that I missed that message.
I'm in the middle of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerrit P. Haase wrote:
Does anybody has an SQLite package ready for review?
2.8 or 3.2? (they can be installed in parallel)
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
Comment: Using GnuPG with Thunderbird -
Vaclav Haisman wrote:
# Boost 1.33.0 Cygwin package setup.hint
sdesc: Boost 1.33.0 main package
ldesc: Boost provides free peer-reviewed portable C++ source libraries.
This is still not the correct format for sdesc and ldesc. You should
not start sdesc with the name of the package. It
Yaakov S wrote:
libIDL2 is ready and just waiting for upload, together with
ORBit-0.5/libIDL-0.6. I'm in the middle of compiling ORBit2-2.10.3.
But these are just point bumps and shouldn't be immediately necessary
for building the backend components (GConf2, gnome-vfs2, libbonobo2,
libgnome2).
Yaakov S wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerrit P. Haase wrote:
Does anybody has an SQLite package ready for review?
2.8 or 3.2? (they can be installed in parallel)
I played with libgda, however I cannot remember which version
is required for libgda.
Gerrit
--
-Original Message-
From: Dave Korn
Sent: Wednesday, August 17, 2005 1:23 PM
Subject: RE: upload: diffstat-1.40-1, tar-1.15.1-1
Original Message
From: Christopher Faylor
Sent: 17 August 2005 18:20
Let's apply some common sense here, too. You specify wt,
what would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerrit P. Haase wrote:
I played with libgda, however I cannot remember which version
is required for libgda.
For libgda-1.0.4, which I've built already, sqlite-2.8. Now that
glib-2.6 is out, I'll try libgda-1.2 and see how that goes.
Yaakov
From: Eric Blake
Sent: Wednesday, August 17, 2005 11:47 AM
To: cygwin-apps@cygwin.com
Subject: Re: upload: diffstat-1.40-1, tar-1.15.1-1
I'm not sure this is correct. fopen(..., rt) should create LF
endings on binary mounts and CRLF on text mounts... IIUC,
the open
mode is a
But opening with rt is non-POSIX,
No it isn't. POSIX requires any CRT that doesn't understand or care about
the second character to ignore it.
This is the POSIX definition of fopen():
http://www.opengroup.org/onlinepubs/009695399/functions/fopen.html
In there, it specifically calls out
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Blake
Sent: Wednesday, August 17, 2005 9:41 PM
To: cygwin-apps@cygwin.com
Subject: RE: upload: diffstat-1.40-1, tar-1.15.1-1
But opening with rt is non-POSIX,
No it isn't. POSIX
50 matches
Mail list logo
