Is there a current list of orphaned packages?
gsw
Charles Wilson wrote:
Williams, Gerald S (Jerry) wrote:
Well, it's already better than the existing rxvt in at least one way:
[...]
Well, maybe so. But sucking 100% CPU *while doing nothing*
is just not acceptable to me -- or, I suspect, to anyone else.
However, my rxvt-unicode-X package
Charles Wilson wrote:
I'm ITP'ing it as a call for assistance, and it'll remain in 'test'
state until libW11 + libXpm-W11 + rxvt-W works as well or better than
the existing rxvt in native mode.
Well, it's already better than the existing rxvt in at least one way:
Have you ever tried running
Warren Young wrote:
If there is a ctags maintainer, please stand up and make yourself
known!
I've also been watching this with interest. Looking in the archives, it
appears that the maintainer listed in the ctags README file put out a
request for a new maintainer in Dec 2003. I've been waiting
Yaakov S (Cygwin Ports) wrote:
IMHO, that was not desirable. Eventually I could imagine X11 and
Cygwin native versions of the same package. I liked this method of
making the distinction.
What does Cygwin native mean? If Cygwin is meant to be a POSIX
environment, then X11 should be the
I remember seeing a question from Brian Ford about this, but
don't remember seeing any answers...
Does anyone know of a good place to post Cygwin packages? My
cable network provider gives me some space, but it's rather
small and I have other uses planned for it.
I ask because I noticed that two
Warren Young wrote:
Rebooting is a cop-out in this case. All the setup program
has to do is stop running services before starting the upgrade.
I didn't mean to imply that rebooting was the best solution,
just that there may be some extra steps involved when you do
the base Cygwin install.
One issue that sometimes pops up currently is the failure of
post-install scripts when Cygwin's DLL is being replaced. I
know that you can run into trouble if a daemon is currently
using the DLL when you update the cygwin package, at least.
Perhaps a two-part install wouldn't be that bad, as long
Igor Pechtchanski wrote:
However, parts of it are released under the Q
Public license, which GNU lists explicitly as
non-GPL-compatible. Does this mean an automatic
no to an official Cygwin package [...] ?
From http://cygwin.com/licensing.html:
In accordance with section 10 of the GPL, Red
Max Bowsher has graciously volunteered to take over the
maintenance of SWIG for Cygwin.
Those of you paying attention to SWIG releases may have
noticed that we haven't had one in a while. About a year
ago, I had to change jobs suddenly when my organization
was disbanded, and I haven't been able
I linked swig (unchanged from swig-1.3.19-1) against
cygwin-1.5.0-1 and it still works (no surprise).
I'm not sure if we should really bother updating it,
since it has no other DLL dependencies and the old
version should therefore continue to work.
I created a 1.3.19-2 version just in case. It's
Corinna Vinschen wrote:
Packages which depend on external libs should be newly build only
if all external libs have been newly build first. E.g. vim depends
on ncurses. So I, the vim maintainer, will wait with creating a new
vim version until Charles, the ncurses maintainer, has
Christopher Faylor wrote:
Rebuild your package.
Run it.
+Does it work?+
/ \
No. Yes.
See if it
A new version of the SWIG package (swig-1.3.19-1) is ready for upload from
the following locations:
Binary: http://home.ptd.net/~gwilliam/cygwin_swig/swig-1.3.19-1.tar.bz2
Source: http://home.ptd.net/~gwilliam/cygwin_swig/swig-1.3.19-1-src.tar.bz2
Or follow the links from:
14 matches
Mail list logo
