On Apr 13 15:35, Christopher Faylor wrote:
On Sun, Apr 13, 2008 at 11:42:46AM +0200, Corinna Vinschen wrote:
We would need to transfer them to the new place or we stick to the
Cygnus Solutions for backward compatibility. I'm not sure we still
need the Program Options thingy. I never heard
On Apr 13 11:49, Dr. Volker Zell wrote:
Corinna Vinschen writes:
Gentoo is not valid since it packs everything, including the kitchen
sink. For Debian we require that it's in stable. But if it's in
Ubuntu, it's ok. Now *somebody* has to review it... hint, hint
Is that
On Apr 13 21:49, Dr. Volker Zell wrote:
wget http://volkerzell.de/cygwin/ITP/transfig/setup.hint
wget http://volkerzell.de/cygwin/ITP/transfig/transfig-3.2.5-1-src.tar.bz2
wget http://volkerzell.de/cygwin/ITP/transfig/transfig-3.2.5-1.tar.bz2
Looks good, uploaded.
Thanks,
Corinna
--
Hi all,
we're now finally starting the release cycle for Cygwin 1.7. Not
everything is in it's place, some changes are still in flux and the
installation is still somewhat bumpy but we should get to all of that
while testing goes on.
We have set up a new release area which is dedicated to the
Corinna Vinschen writes:
On Apr 13 21:49, Dr. Volker Zell wrote:
wget http://volkerzell.de/cygwin/ITP/transfig/setup.hint
wget
http://volkerzell.de/cygwin/ITP/transfig/transfig-3.2.5-1-src.tar.bz2
wget http://volkerzell.de/cygwin/ITP/transfig/transfig-3.2.5-1.tar.bz2
On Apr 14 15:26, Dr. Volker Zell wrote:
wget http://volkerzell.de/cygwin/ITP/xfig/setup.hint
wget http://volkerzell.de/cygwin/ITP/xfig/xfig-3.2.4-7-src.tar.bz2
wget http://volkerzell.de/cygwin/ITP/xfig/xfig-3.2.4-7.tar.bz2
cd xfig-lib
wget
On Mon, Apr 14, 2008 at 03:11:56PM +0200, Corinna Vinschen wrote:
Hi all,
we're now finally starting the release cycle for Cygwin 1.7. Not
everything is in it's place, some changes are still in flux and the
installation is still somewhat bumpy but we should get to all of that
while testing goes
On Mon, Apr 14, 2008 at 11:56:28AM +0200, Corinna Vinschen wrote:
On Apr 13 15:35, Christopher Faylor wrote:
On Sun, Apr 13, 2008 at 11:42:46AM +0200, Corinna Vinschen wrote:
We would need to transfer them to the new place or we stick to the
Cygnus Solutions for backward compatibility. I'm not
On Apr 14 10:39, Christopher Faylor wrote:
On Mon, Apr 14, 2008 at 03:11:56PM +0200, Corinna Vinschen wrote:
Hi all,
we're now finally starting the release cycle for Cygwin 1.7. Not
everything is in it's place, some changes are still in flux and the
installation is still somewhat bumpy but
On Mon, Apr 14, 2008 at 05:27:58PM +0200, Corinna Vinschen wrote:
On Apr 14 10:39, Christopher Faylor wrote:
On Mon, Apr 14, 2008 at 03:11:56PM +0200, Corinna Vinschen wrote:
Hi all,
we're now finally starting the release cycle for Cygwin 1.7. Not
everything is in it's place, some changes
On Apr 14 11:42, Christopher Faylor wrote:
On Mon, Apr 14, 2008 at 05:27:58PM +0200, Corinna Vinschen wrote:
Oh, hmm, I assumed you would do that anyway at one point.
It will be a pain in the neck to do it if people start updating the
current cygwin-2 directory while I'm trying to perfect
The most important changes on the user level are the long path name
support including UTF-8 character support, as well as IPv6. Other
changes are also important, but these two will likely have the most
impact. I'd like to ask you to keep an eye especially on them when
building and testing.
On Sat, 12 Apr 2008, Brian Dessent wrote:
Unresolved issues with this plan:
- What are we going to do about text/binary mode? To maintain the
setting, setup would have to be taught to parse/write fstab. Ugh. Plan
B would be to say that if you want textmode you have to edit fstab
Christopher Faylor wrote:
Yes, I know. I just don't think it clarifies anything to put a Red
Hat in the registry.
I was thinking Cygwin would be better as well, but since it is
supposed to be a two-level heirarchy how about
HK{LM,CU}\Software\Cygwin Project\Cygwin. It has always seemed to me
Igor Peshansky wrote:
But one thing to consider is that by adding a registry key, we're setting
things up for one dominant installation of Cygwin. So people juggling
multiple installations really *will* have to go edit the registry to
switch -- no more nice mount -m approach, since the
Andrew Schulman wrote:
(1) Do all packages that include compiled code need to be rebuilt for Cygwin
1.7? IOW, is ABI compatibility broken from 1.5? Also, I presume that there
would be no need to rebuild any packages that don't include compiled code,
e.g.
packages that depend only on Perl
16 matches
Mail list logo
