Re: [ITA] fftw3

--- Brian Dessent ha scritto: > Brian Dessent wrote: > > > > Charles Wilson wrote: > > > > > As no one was actually able to install this > file, is it OK to replace it > > > on sourceware (perhaps deleting the .md5sum > file) without bumping the > > > version number? > > > > Yes, I considered

[wwwdocs patch] mention cygport as "method three"

This is a patch for to officially mention cygport as acceptible. Brian2008-04-08 Brian Dessent <[EMAIL PROTECTED]> * setup.html: Mention cygport as method three. Index: setup.html === RCS fi

Re: [ITA] libXft/libXft2/libXft-devel-2.1.7: A client-side font API for X applications

Brian Dessent wrote: > As Angelo tried to report on the wrong mailing list, this is totally > broken. How are you supposed to compile any X11 apps after installing > this package, without manually adding -I/usr/X11R6/include/X11 to > CPPFLAGS? Simply installing libXft-devel causes all the X11 he

Re: [ITA] libXft/libXft2/libXft-devel-2.1.7: A client-side font API for X applications

"Dr. Volker Zell" wrote: > This package likes to install the header files to > > /usr/include/X11/Xft/*.h > > xorg-x11-devel installs a symlink > > /usr/include/X11 -> ../X11R6/include/X11 > > Given that the X11 hierarchy is deprecated, I like to remove this > symlink in a preremove script

Re: [ITA] fftw3

On Tue, Apr 08, 2008 at 06:33:40PM -0700, Brian Dessent wrote: >Brian Dessent wrote: >>Charles Wilson wrote: >>>As no one was actually able to install this file, is it OK to replace >>>it on sourceware (perhaps deleting the .md5sum file) without bumping >>>the version number? >> >>Yes, I considered

Re: [ITA] fftw3

Brian Dessent wrote: > > Charles Wilson wrote: > > > As no one was actually able to install this file, is it OK to replace it > > on sourceware (perhaps deleting the .md5sum file) without bumping the > > version number? > > Yes, I considered doing that myself. Sounds like a good idea. Crap. I

Re: [ITA] fftw3

Charles Wilson wrote: > As no one was actually able to install this file, is it OK to replace it > on sourceware (perhaps deleting the .md5sum file) without bumping the > version number? Yes, I considered doing that myself. Sounds like a good idea. Brian

Re: [ITA] fftw3

Brian Dessent wrote: --- Cygwin Setup --- Can't open file://C:\Downloads\packages\cygwin/release/_obsolete/fftw3-dev/fftw3-dev-3.1.2-2.tar.bz2 for reading: Invalid or unsupported tar format --- OK

Re: [ITA] fftw3

Marco Atzeri wrote: > are the needed setup.hint and empty package > > http://matzeri.altervista.org/cygwin/_obsolete/fftw3-dev/setup.hint > http://matzeri.altervista.org/cygwin/_obsolete/fftw3-dev/fftw3-dev-3.1.2-2.tar.bz2 It appears that you bzipped a 0-byte .tar file. This won't work. You ne

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

Corinna Vinschen wrote: > Sorry, but I didn't remember that. Why didn't you just tell us? I thought we were talking about two different things. As I see it, here are the *conceptual* things we're dealing with: A) We want to have a tree of packages that is still usable for users of 9x/ME after

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Apr 8 23:46, Corinna Vinschen wrote: > On Apr 8 14:16, Brian Dessent wrote: > > Okay, so, several years ago setup.exe HEAD was modified to look for > > "release" and "release_legacy" as the base dirname for packages > > depending on whether it was running on 9x/ME or NT/2k/etc. I understand >

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Apr 8 17:39, Christopher Faylor wrote: > On Tue, Apr 08, 2008 at 11:07:26PM +0200, Corinna Vinschen wrote: > >With a dash? cygwin-ng? Like syslog-ng. I was going to suggest this > >too, but I didn't want to copy the naming too bluntly. > > We actually use "ng" internally to Netapp. I actua

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Apr 8 14:16, Brian Dessent wrote: > Corinna Vinschen wrote: > > > Why, we could always name the next versions "cygwin-newer", > > "cygwin-evenmorenew", "cygwin-newerthannew" and > > "cygwin-reallyreallynew-imeanit". > > > > > How about cygwinng? > > > > With a dash? cygwin-ng? Like syslog-

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Tue, Apr 08, 2008 at 11:07:26PM +0200, Corinna Vinschen wrote: >On Apr 8 14:41, Christopher Faylor wrote: >> On Tue, Apr 08, 2008 at 07:40:13PM +0200, Corinna Vinschen wrote: >> >On Apr 8 13:26, Christopher Faylor wrote: >> >> cygwin-xp? cygwin-2008? >> > >> >cysta? :) >> > >> >cygwin-2008 is

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

Corinna Vinschen wrote: > Why, we could always name the next versions "cygwin-newer", > "cygwin-evenmorenew", "cygwin-newerthannew" and > "cygwin-reallyreallynew-imeanit". > > > How about cygwinng? > > With a dash? cygwin-ng? Like syslog-ng. I was going to suggest this > too, but I didn't wan

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Apr 8 14:43, Christopher Faylor wrote: > On Tue, Apr 08, 2008 at 02:34:03PM -0400, Charles Wilson wrote: > >If we do choose to name the release directory "cygwin-2008", we probably > >ought to try to get cygwin-1.7 out the door before, say, Christmas, tho. > > > > Uh oh. I'm hyperventilating

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Apr 8 14:41, Christopher Faylor wrote: > On Tue, Apr 08, 2008 at 07:40:13PM +0200, Corinna Vinschen wrote: > >On Apr 8 13:26, Christopher Faylor wrote: > >> cygwin-xp? cygwin-2008? > > > >cysta? :) > > > >cygwin-2008 isn't bad, though. > > > >> cygwin-nextgen? > > > >Or just cygwin-new, maybe

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Tue, Apr 08, 2008 at 02:34:03PM -0400, Charles Wilson wrote: >If we do choose to name the release directory "cygwin-2008", we probably >ought to try to get cygwin-1.7 out the door before, say, Christmas, tho. > Uh oh. I'm hyperventilating now. Actually, given what is going into cygwin-1.7, th

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Tue, Apr 08, 2008 at 07:40:13PM +0200, Corinna Vinschen wrote: >On Apr 8 13:26, Christopher Faylor wrote: >> On Tue, Apr 08, 2008 at 06:26:46PM +0200, Corinna Vinschen wrote: >> >On Apr 4 14:15, Corinna Vinschen wrote: >> >> On Apr 3 20:49, Christopher Faylor wrote: >> >> > [responding to the

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Tue, Apr 08, 2008 at 13:26:46 -0400, Christopher Faylor wrote: >On Tue, Apr 08, 2008 at 06:26:46PM +0200, Corinna Vinschen wrote: >>I'm just not sure we should really call it "cygwin-1.7". What would >>be a good name, which does not refer to the actual version number? >> >> "Cygwin" with upper

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Apr 8 13:26, Christopher Faylor wrote: > On Tue, Apr 08, 2008 at 06:26:46PM +0200, Corinna Vinschen wrote: > >On Apr 4 14:15, Corinna Vinschen wrote: > >> On Apr 3 20:49, Christopher Faylor wrote: > >> > [responding to the thread which started it all] > >> > On Wed, Apr 02, 2008 at 02:35:51PM

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Tue, Apr 08, 2008 at 06:26:46PM +0200, Corinna Vinschen wrote: >On Apr 4 14:15, Corinna Vinschen wrote: >> On Apr 3 20:49, Christopher Faylor wrote: >> > [responding to the thread which started it all] >> > On Wed, Apr 02, 2008 at 02:35:51PM +0200, Corinna Vinschen wrote: >> > >- We create a f

Re: [HEADSUP] Let's start a Cygwin 1.7 release area

On Apr 4 14:15, Corinna Vinschen wrote: > On Apr 3 20:49, Christopher Faylor wrote: > > [responding to the thread which started it all] > > On Wed, Apr 02, 2008 at 02:35:51PM +0200, Corinna Vinschen wrote: > > >- We create a ftp://cygwin.com/pub/cygwin-1.7 dir. > > > > > >- Under that dir, we cre