FYI, the power supply on my development computer went. I'll be AFK
until I can get a replacement, hopefully sometime next week.
Yaakov
Cygwin/X
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
The gc package at least might be useful for others as well.
If by gc you mean the Boehm-Demers-Weiser garbage collector library,
it's already packaged as libgc.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jon TURNEY wrote:
The Bitstream Vera TTF font family has gone AWOL in the upgrade to X.Org R7.4
(it was previously contained in the xorg-x11-fscl package)
Which makes me wonder if there are other such cases...
If possible, the stub
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
I hope I catched everything. Would you mind to take a quick look?
lesstif was broken up, adding libXm2 and libXm-devel. AFAICS that's
everything.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
I'm trying to keep track of the maintainership changes due to the
new X.Org stuff but I'm somewhat overwhelmed by the mere number.
:-)
I assume the entire X.Org subdir and all of its packages are yours
right now. Are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jan Nieuwenhuizen wrote:
Ouch. Sorry for the late response, please adopt and go ahead.
No problem. Thanks,
Yaakov
Cygwin/X
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I propose to add giflib to (mostly) replace libungif (which is currently
mine). The latter is no longer maintained because there are no
remaining legal impediments to using giflib.
The only difference between these packages is the name of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package maintainers,
Modular X11 has been pushed into the distro. I need all maintainers of
X11-related packages to update their installation and test their
packages to make sure they still work correctly.
Yaakov (Cygwin Ports) wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin Ports) wrote:
4) An announcement will be made on cygwin-xfree-announce@ with all the
details.
I sent an announcement this morning, and it showed on
cygwin-xfree-announce@, but it wasn't echoed to [EMAIL PROTECTED] The last
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
Can you hold off uploading until X11 is in place (hopefully by
tomorrow)? I'm having enough trouble keeping the staging area in sync
with release as it is.
Sure.
X11 is in place now, so whenever you're ready.
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
upset: *** setup-2.ini: warning - package ORBit2-devel requires non-existent
package minires-devel
upset: *** setup-2.ini: warning - package atk requires non-existent package
glib2-runtime
upset: *** setup-2.ini:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
The mktemp package is obsolete. It comes from coreutils these days.
Then the transition wasn't correctly handled, because the latest
mktemp-1.5-4 is a real package. An empty 1.5-5 package should have been
created at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
I'm on it.
Can you hold off uploading until X11 is in place (hopefully by
tomorrow)? I'm having enough trouble keeping the staging area in sync
with release as it is.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Even the rollup patch?
ftp://invisible-island.net/${PN}/${PV}/${PN}-${PV}-20060909-patch.sh.bz2
Yes.
It only breaks the ABI (B?) if you do it the way you suggested:
http://cygwin.com/ml/cygwin/2008-05/msg00038.html
Yes,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
They were called rollup patches. T.E.D. releases patches roughly every
week, and then every month (or two, or three), he combines all patches
dating back to an official release into a rollup patch -- and these
rollup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew Schulman wrote:
Several of my packages require multiple patches to compile and run properly in
Cygwin. Instead of maintaining them all together as One Big Patch, I find it
easier to manage them as individual, discrete patch files, and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Okay, so these are (mostly) your own custom patches needed to port the
code to cygwin, and not official patches from somewhere else, like
1) bugfixes taken wholesale from another distro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin Ports) wrote:
Good; there are no other messages from upset in the staging area. All I
need then is permission to adopt fontconfig and lesstif.
Just waiting for fontconfig now. ITA sent five days ago and no response
from Jan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ralph Hempel wrote:
Hmmm - I never thought to look there, apparently you've
done a lot of the work already :-)
And looking at the ports list, it seems that all the libs I
was hoping to port over are already there!
I'm not exactly sure what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
http://cygwin.com/acronyms/#PCYMTWLL
André Bleau wrote:
The applications using freeglut can be compiled and linked without problems,
but I now realize that native GLUT applications cannot be compiled
correctly if the libglut-devel package is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André Bleau wrote:
This cannot work as the order of system directories cannot be changed by -I.
Oops.
What could be done is that I update the opengl package with an additionnal
directory:
/usr/include/opengl that will contain only a symbolic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
Incidentally, I set up a scratch area:
/sourceware/snapshot-tmp/yselkowitz
Thanks for setting up the staging area. Looks like everything is ready
now, EXCEPT:
1) I get PROBLEMS WITH errors on the new xorg-x11-* empty
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I hereboy propose to take maintainership of Cygwin/X.
It was over two years ago that I started to work on the (then brand-new)
modular X11, and it was indeed in consideration of the sheer number of
packages involved that I created cygport. Both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Yaakov (Cygwin Ports) wrote:
I hereboy propose to take maintainership of Cygwin/X.
s/hereboy/hereby/
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package maintainers,
Please find attached a list of binary packages which currently list a
dependency on monolithic xorg-x11-* packages, together with their new
dependencies as I could best determine.
Please review this list and:
* Let me know if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
Why can't you just associate the source
package with one of the two existing binary packages instead of
inventing a third, empty, hidden package to associate it with?
But I still think this makes more sense.
Because this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
If it really does save you time than I remove my objection. Can I just
request that the sdesc of such packages say something informative and
explicit about their purpose, e.g.:
sdesc: X.Org Xfixes library (dummy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
Yes, unless you want the package to go to Misc, which is wrong. But I
don't see any reason to hide anything. Just sdesc it as Sources for
BLAH. It won't be installed unless the user specifically chooses it.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jan,
As part of the X11 transition, I would like your permission to take over
the fontconfig package. fontconfig is used by the fonts, which I will
be maintaining as part of X11 and are being relocated. It is also
dependency-sandwiched between my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian,
As part of the X11 transition, I would like your permission to take over
the lesstif package. It is a dependency of libGLw from Mesa, which will
be part of the modular X11 upgrade, as well as a number of other X11
packages whose
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
Yes, unless you want the package to go to Misc, which is wrong. But I
don't see any reason to hide anything. Just sdesc it as Sources for
BLAH. It won't be installed unless the user specifically chooses it.
I tried
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jari,
As part of the X11 transition, I would like your permission to take over
the xterm package. It's presence is assumed as part of a base X
installation, and is called from the standard startup scripts.
I would immediately update xterm to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
This sounds promising. Thank you very much for working on this!
It appears now that we won't have to wait for cygwin-1.7 after all; the
latest X11R7.4 should be ready for ITA in the next few weeks, if not sooner.
Yaakov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
Hmm. Very good idea but I got a unable to decrypt the certificate id
when I clicked there. Does anyone else have this problem?
The link WFM in Firefox 3; didn't try going any further than that.
Yaakov
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've just made cygport-0.9.3 available in release-2 with the following
changes:
* PV is now an array; members 1-* replace PVP[].
* foo_CONTENTS can now be used in place of PKG_CONTENTS[].
* cygtest(): Doesn't exit when tests fail.
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
ORPAHNED: apache2
Lapo Luchini: lighttpd
Reini Urban: clamav
Charles Wilson: tiff, unzip
any news here?
lighttpd was updated on 20 October.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
So...should cygwin-1.7 packages all be built using gcc-4.x, or not? (And
is it really, as I fear, an all-or-nothing proposition given the libgcc
changes?)
I'm not sure how much this is all-or-nothing for C, but I imagine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
ACK. I would personally spend a couple of gold stars for Yaakov and
the guy(s) who help Yaakov to get the X11R7 server side up to speed.
Promised!
FYI, Jon Turney has stepped up on the cygwin-ports-general list with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Unfortunately we haven't made any progress since my last update two
weeks ago, and now there's a new vulnerability (clamav).
By maintainer
=
ORPAHNED: apache2
Lapo Luchini: lighttpd
Reini Urban: clamav
Charles Wilson: tiff, unzip
By
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've just made cygport-0.9.2 available in release-2 with the following
changes:
* SRC_URI: now accepts SRPMs.
* PATCH_URI: now accepts multiple-patch tarballs.
* Installs documentation into /usr/share/doc/PACKAGE.
* Removed support for libtool-1.5.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Package maintainers,
Thank you to those who have updated your packages for the last batch of
security vulnerabilities. There are two newly announced
vulnerabilities, including one orphaned package which needs some help:
By maintainer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Well, it's water under the bridge now: I'm pretty happy with
libtool-2.2.x. I think after the upcoming 2.2.6 release I'll officially
stop supporting libtool-1.5.x, clean out the libltdl3/ directory of all
but the most
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
Shouldn't this have a major version bump?
* Runs only on Cygwin 1.7.
* All managed mount code has been removed.
* cygclasses are now installed into ${datadir}/cygport/cygclass.
That was the justification for jumping from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've just made cygport-0.9.1 available in release-2 with the following
changes:
* dolib(): Installs *.la with libtool.
* inherited(): New function.
* Use fully qualified paths within all postinstall/preremove scripts.
* autotools.cygclass:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
Setup.exe for 1.5 is unchanged, afaik.
Yeah, I noticed. Annoying, too. :-(
I tweaked setup for 1.7 (CVS HEAD) so that it shouldn't complain
anymore about any type of empty tar file.
I have no idea if there was a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
You should probably upload a new version soon; 0.9.0-1 is
missing files from the binary tarball:
I've just uploaded 0.9.0-2 to release-2 accordingly.
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
Can we also make this version avoid the broken lndir.exe?
http://cygwin.com/ml/cygwin/2008-06/msg00056.html
I rebuilt and tested the X11R7 lndir on 1.7, and unfortunately it seems
to have the same bug. I would prefer to fix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
New uploads:
http://cygwin.cwilson.fastmail.fm/ITP/lzma-4.32.7-1-src.tar.bz2
http://cygwin.cwilson.fastmail.fm/ITP/lzma-4.32.7-1.tar.bz2
http://cygwin.cwilson.fastmail.fm/ITP/liblzmadec0-4.32.7-1.tar.bz2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
Other *NIX behave the same way, if they do not populate st_nlink
to 1 for directories (for example, I believe this is how Linux handles
FAT filesystems, so the same lndir bug would be present there).
Findutils already had to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
cgf and/or Corinna, could I get your official opinion on these, so that
I can proceed with the necessary changes to cygport trunk if agreed:
This one gets into the legal category:
As for license files, do we really need to install hundreds of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
My linux systems have a bunch of LICENSE* files in /usr/share/doc. I
think it is safer to leave them there, even though no one ever reads
them.
Fine. What about the docdir change?
Yaakov
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Looks as swig is orphaned and out-of-date. I'll take it:
http://ftp.sunsite.dk/projects/cygwinports/release/swig/swig-1.3.36-1-src.tar.bz2
http://ftp.sunsite.dk/projects/cygwinports/release/swig/swig-1.3.36-1.tar.bz2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jari Aalto wrote:
I have no objection of dropping Cygwin 'lzma' package if you take over
the maintenance. The SDK + Debian patches (GNU --long option interface)
is pain to maintain because the SDK uses windows style CRLF.
+1. Replacing the SDK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
One of these days, I'll learn to check cygwin-ports before porting a new
package.
I do make the repository available for a reason, you know. :-)
http://cygwin.cwilson.fastmail.fm/ITP/lzma-utils-4.32.7-1-src.tar.bz2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Libarchive is a programming library that can create and read several
different streaming archive formats, including most popular tar
variants and several cpio formats. It can also write shar archives and
read ISO9660 CDROM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
Done. CVS setup.exe now supports .tar.lzma files.
Is this intended to be the default now? Should I change cygport trunk
accordingly?
Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
What if we add an obsoletes: line to setup.{ini,hint}?
The idea is that you don't have to provide empty replacement packages
for the old packages anymore, and setup removes all packages noted in
the obsoletes: line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
upset: *** warning package gnome-common requires non-existent package
gnome-doc-utils
upset: *** warning package gnome-common requires non-existent package
gnome-doc-utils
This is mine; gnome-doc-utils isn't in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
Personally I'm kind of not interested to go this road. If I learn about
a problem in an upstream package, I update. If anybody else want's to
take over responsibility for security problems, I certainly don't stand
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Before packagers start focusing on 1.7, it appears that we still have a
number of security updates required for the 1.5 tree:
By maintainer
=
ORPAHNED: apache2
Jari Aalto: mercurial, pngcrush, python-paramiko
Lapo Luchini: lighttpd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
I hate to suggest another mailing list but I wonder if we should have
another unarchived, closed list for discussing security issues. The
recent setup.exe problem got me thinking that we might need something
like this.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A few ideas about package documentation for 1.7:
1) Info pages
Per a recent discussion on the main list, GNU info 'dir' will be managed
solely by _update-info-dir. Packagers should no longer use postinstall
scripts for this purpose; the next
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
| Any reason this version insists on maximizing itself when going to the
| package selection screen, rather than remaining at the size of the
| previous screen?
Because someone programmed it that way. :-)
For the record, while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Perhaps I screwed something up with my patches which worked before,
| but it worked fine for me, so I don't know. Please give it a try
| and report back.
Thanks!
I haven't tested it extensively, but I was able to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Now that 7.2 is final we can put this plan into realization.
Thanks, here you are:
http://ftp.sunsite.dk/projects/cygwinports/release/GNOME/gvim/gvim-7.2-1-src.tar.bz2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Packaging looks ok to me, but why the dependency to rcs?!?
It was based on the Gentoo ebuild's deps, but digging deeper, it seems
as with at least this version it's optional. I'll remove it before
moving it into release.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Rothenberger wrote:
| I'm ITP'ing this in preparation for packaging subversion-1.5.1.
|
| serf[1] is included in Debian testing[2], but I could not find it in
| Fedora or SuSE.
Probably because subversion-1.5 itself is only in testing.
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Almost six weeks ago, Corinna Vinschen wrote:
| I have no idea. 7.2a is the first beta. But vim is otherwise very
| stable so I don't expect more than another beta. If I might venture a
| guess, I'd say, (much) less than 4 weeks.
Or maybe not.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Rothenberger wrote:
| I'm confused by this. You're suggesting that I have the following?
|
| * serf0: empty
| * libserf0_0: DLL and docs
| * libserf0-devel: headers and link libraries
|
| Why do I need serf0?
Because the package needs a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Rothenberger wrote:
| I've updated the packaging to address Yaakov's suggestions, although
| I used serf as the package name for the empty (source) package
| instead of serf0.
|
| Updated hints and files are below. I think I have two votes to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| are you still with us? There was a joe problem reported on the main
| list two weeks ago.
Jari,
There are also outstanding security issues with three of your packages:
mercurial: Directory traversal (CVE-2008-2942)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Having just used cvs2svn to successfully migrate Ports, I think it would
make a good addition to the distro.
An older version is currently in Debian stable[1]; this version is in
testing[2].
[1] http://packages.debian.org/etch/cvs2svn
[2]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
| I've got libgcc shared and working fine and correctly, either with a
| separate static libgcc_eh, or with it shared, although that's only an
option
| if you also have shared libstdc++.
|
| Getting libstdc++ to work shared is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| - Creating filenames with special DOS characters '', '*', ':', '',
| '', '|' is supported.
|
| - Creating files with special DOS device filename components (aux,
| nul, prn) is supported.
|
| - File name are case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| setup is a Win32 application. It won't know about this. Thou shalt
| not create packages which rely on case-sensitivity as part of the
| net distro.
That's what I thought. So while managed mounts will no longer be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Illegal? The only illegal chars are slash and backslash, even on
| case-insensitive mounts. Does it really occur often that you have two
| filenames in the same dir only differing by case?
For Cygwin I understand that,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| What if we add an obsoletes: line to setup.{ini,hint}?
|
| The idea is that you don't have to provide empty replacement packages
| for the old packages anymore, and setup removes all packages noted in
| the obsoletes: line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| are you still with us? There was a joe problem reported on the main
| list two weeks ago. It looks like you're still not subscribed to the
| cygwin mailing list. How do you think you can help users and find out
| about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Our X11R6 hasn't been updated in almost three years now. Since then,
X.org has moved to a modular R7 where each library, executable, font
set, etc. have their own autotooled package.
It seems that our X11 is used for two different things: 1) to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
| It seems like maybe another change to setup.exe would be in order here
| or maybe there could be a base package which did any cleanup required to
| purge unneeded packages.
Could setup-1.7 know if the last installation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| Honestly, I don't know. Maybe it isn't. But so far I'm still thinking
| that a parallel 1.7 install should only be a temporary solution for
| developers and maintainers. It's not something I would like to drag
| on for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| I'm not sure if there's really a big difference between these two points.
| Since we're using two different installation directories, we can get rid
| of old cruft, if we just look carefully what's still used and what not.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| When 1.7 goes gold, the idea is to install over an 1.5 install. Or not.
| It's the choice of the user. Installing over 1.5 is supported by the
| base-cygwin package, which is supposed to convert the registry mount
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As we start preparing for 1.7, I know that until now the focus has been
on the development of Cygwin itself. I'll admit that I know little
about Cygwin's internals, and hence have contributed very little to the
DLL itself, but I do very much
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I would like to make some proposals as to setting up the development
toolchain for 1.7:
1) binutils
Thanks to cgf, we've got a current binutils available now; I'm not sure
if binutils itself benefits from 1.7 (save the long path handling).
There
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nathan Thern wrote:
| I'm getting ready to ITP chicken scheme, but I would like to know what
| exactly does he mean by debian links?
URL on packages.debian.org showing that the package you ITP is in stable
(etch). A package which is in debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nathan Thern wrote:
| OK, the chicken version in etch is 2.3, and the version I want to ITP
| is 3.3. Does that matter?
Generally it hasn't, assuming that 2.3 and 3.3 are basically the same
animal. :-)
Yaakov
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| again I would like to encourage the Cygwin maintainers, to try the new
| Cygwin 1.7.0 release and to look for problems in their packages which
| might be a result of the fairly massive changes in Cygwin 1.7. I
| attached
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Corinna Vinschen wrote:
| ICU is really a build requirement for perl6? If so, I have a hard time
| to require 5 votes for this package...
|
| Anyway, let's start here: +1
I will point out that the previous version of icu is in Debian stable:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
| Yaakov already updated his cygports to this version.
| I need test versions be uploaded.
| I'll switch the hints then from test to curr.
|
| I only see perl-Tk, postgresql-perl, perl-Locale-gettext and
| perl-ExtUtils-*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Rothenberger wrote:
| 1.4.6 won't build with libtool 2.x.
Why not? I've been working with 2.2.2 since it's release, and just
about anything else builds with 2.x, even if originally packaged with 1.5.
Yaakov
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
| I see. To summarize:
| DynaLoader.o is contained in libperl.dll.a,
| Win32CORE.a not.
| ExtUtils::Embed ldopts is correct, but not libtool compatible.
So far, correct.
| Note: the next -e 'cmd' looks weird, but is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
| I tried both ways.
| The standard perl way with Win32CORE.a explicitly added to
| the linker line via $Config{static_ext}, and
Of course, but that makes things difficult when linking *other packages*
against libperl with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Reini Urban wrote:
| Current changes from -3 to -4:
| No API changes, just one added DynaLoader.o in libperl and added one
| missing Win32CORE.a, so your packages will be fine.
I'll admit that I know nothing of Perl internals, but could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
| automake's dist-lzma already functions if you install lzma (I know,
| because I used it when creating m4 1.4.10b); automake uses 'tar | lzma'
| rather than 'tar --lzma'.
Furthermore, 'make distcheck' uses 'unlzma | tar'. Our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dave Korn wrote:
| Your sense of timing is perfect. I just spent an evening trying to
build
| this myself and finally got going with some half-working crudely
limping along
| static build...
It's been in Ports for over a year...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Warren Young wrote:
| Is there a way I can get Cygport to generate this patch for me? It
| seems like it should be able to take the source package, the README, and
| the setup.hint and generate the patch during the prep stage. I can't
| see how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Charles Wilson wrote:
| Not an error. dlopen'ed modules -- such as m4-2.0 and perhaps
| ImageMagick/GraphicsMagick -- might be named .dll but will live in
| /usr/lib/somewhere/
HUNDREDS of packages have dlopen'ed modules:
$ find /usr/lib -name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Dessent wrote:
| - setup.hint missing any of: sdesc, requires, category
Some -doc packages don't have any requires.
| - contains postinstall/preremove script without requiring bash (this
| matters for the order in which scripts are run)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher Faylor wrote:
| - Existence of /usr/man, /usr/doc rather than /usr/share/man
/usr/share/doc.
Also /usr/info.
| - Missing /usr/share/doc/Cygwin/* (probably a warning).
Most of the time when building foo/libfooX/libfoo-devel packages,
1 - 100 of 153 matches
Mail list logo
