headers
Lapo Luchini | 1 Sep 2007 13:25
Picon
Favicon
Gravatar

[upload] typespeed-0.6.2-1

http://cyberx.lapo.it/cygwin/typespeed/setup.hint
http://cyberx.lapo.it/cygwin/typespeed/typespeed-0.6.2-1-src.tar.bz2
http://cyberx.lapo.it/cygwin/typespeed/typespeed-0.6.2-1.tar.bz2
(and usual *.sig GPG signatures on them)

It install the high score file in /var/games/typespeed.score.
Do you think that's good?
Or where else?

setup.hint updated with (requires += libintl2):

sdesc: "Test your typing speed, and get your fingers' CPS"
ldesc: "Typespeed gives your fingers' cps (total and correct), typoratio
and some
points to compare with your friends.
Typespeed's idea is ripped from ztspeed (a dos game made by Zorlim). Idea
of the game should be clear to anyone, just type and type it fast, or be a
lewser."
category: Games
requires: cygwin libintl2 libncurses8

--

-- 
Lapo Luchini
lapo@... (OpenPGP & X.509)
www.lapo.it (Jabber, ICQ, MSN)
Permalink | Reply | 1 comment |
headers
Eric Blake | 1 Sep 2007 14:11
Gravatar

Re: missing xterm dependency?


According to Christopher Faylor on 8/31/2007 8:41 AM:
>> Run 'cygcheck emacs' and see if it reports any missing DLLs.  If so, find
>> this missing package(s) you need to install via 'cygcheck -p <missing DLL
>> name>'.  Rerun 'setup.exe' and install those packages.  Try again.
> 
> Thank you for your help, it wprks now.  Turns out the missing dll was
> cygtiff4.dll, which is in the libtiff4 package. 

OK, so the problem is that emacs 21.2-13 depends on libtiff4, but 22.1-3
depends on libtiff5.  For now, I've added both versions of the library to
the setup.hint (since I don't know of any way to make the library
dependency version-specific), and we can change setup.hint later once
emacs 22 is promoted to current.

--
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@...
Permalink | Reply | 501 comments |
headers
Eric Blake | 1 Sep 2007 14:17
Gravatar

Re: [upload] typespeed-0.6.2-1


According to Lapo Luchini on 9/1/2007 5:25 AM:
> http://cyberx.lapo.it/cygwin/typespeed/setup.hint
> http://cyberx.lapo.it/cygwin/typespeed/typespeed-0.6.2-1-src.tar.bz2
> http://cyberx.lapo.it/cygwin/typespeed/typespeed-0.6.2-1.tar.bz2

Uploaded, leaving 0.4.4-2 as previous.  Do you want 0.4.4-1 deleted?

> It install the high score file in /var/games/typespeed.score.
> Do you think that's good?

http://www.pathname.com/fhs/pub/fhs-2.3.html#VARGAMESVARIABLEGAMEDATA says
that is the right place.

--
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@...
Permalink | Reply | 0 comments |
headers
Phil Nelson | 4 Sep 2007 21:54
Picon

[itp] Coda filesystem

Hello,

   This is a request for feedback on whether adding the packages that
make up the Coda filesystem would be something that would be supported.
I haven't taken the time to produce the packages yet, but would like to know
whether it would be "worth my time" to do so.

   Current state:  
         Coda is a distributed file system (http://coda.cs.cmu.edu) that has run
on UNIX-like systems for a long time.  There is currently active support for
Linux and NetBSD with some moderate support for FreeBSD.    Over the 
past few years, there has been development of a kernel module for 
Windows that has now reached a point of stability that makes Coda run well
in Windows.

         Coda for Windows would not work without Cygwin because the kernel
module passes requests to get files from the file server to a user space
daemon, venus. While there are some changes to venus for the Windows 
environment, venus still  can not run without cygwin.   The same is true for
most of the user-land binaries that support the Coda filesystem.

         CMU currently runs a private mirror of the cygwin distribution that 
includes two local packages, coda-base and coda-devel.   coda-base is all
the cygwin binaries required and coda-devel is a "meta package" that just
exists to provide the prerequisites to rebuild the coda-base package.    There
is also special built .exe that is distributed on the Coda ftp site that provides
for the kernel module installation and  configuration of a Coda client.    
(coda-base is part of base in this private mirror since the sole reason
for the mirror is to support Coda.)
(Continue reading)

Permalink | Reply | 5 comments |
headers
d.henman | 5 Sep 2007 00:53
Picon

Re: [itp] Coda filesystem


I am not an expert of current distributed files systems, but for cygwin wouldn't 
MogileFS be easier to implement (even though its not a fs in and of itslef). From my understanding it only
requires perl and mysql I believe.

Ref:  http://www.danga.com/mogilefs/

Phil Nelson <phil@...> wrote:
> Hello,
> 
>    This is a request for feedback on whether adding the packages that
> make up the Coda filesystem would be something that would be supported.
> I haven't taken the time to produce the packages yet, but would like to know
> whether it would be "worth my time" to do so.

Regards,
  Darel Henman
Permalink | Reply | 1 comment |
headers
Phil Nelson | 5 Sep 2007 02:02
Picon

Re: [itp] Coda filesystem

On Tuesday 04 September 2007 3:53:17 pm d.henman wrote:
> I am not an expert of current distributed files systems, but for cygwin wouldn't 
> MogileFS be easier to implement (even though its not a fs in and of itslef). From
> my understanding it only requires perl and mysql I believe. 
> 
> Ref:  http://www.danga.com/mogilefs/

The real intent of my questions was more like:

   We are already managing cygwin packages in a private
cygwin mirror for Coda.   We would like to make the packages
be on all cygwin mirrors.

I wasn't asking just to bring in a distributed file system.   And
Coda and MogileFS are not really similar file systems.

From the web site:

 " you don't run regular Unix applications or databases against MogileFS.
 It's meant for archiving write-once files and doing only sequential reads."

While you can't have a database file in Coda either,  Coda is a full R/W
distributed file system with "disconnected operation".   But I don't want
to end up in a discussion of Coda vs any other FS, I just wanted a 
discussion of inclusion of Coda or not.

--Phil

--

-- 
Phil Nelson (phil@...) http://www.cs.wwu.edu/nelson
(Continue reading)

Permalink | Reply | 0 comments |
headers
Reini Urban | 5 Sep 2007 07:08
Picon
Gravatar

Re: [itp] Coda filesystem

Phil Nelson schrieb:
...
>          To support Coda as a standard part of Cygwin I would propose
> the following packages:
> 
> 	lwp  (Libs)  -- A Coda specific light weight process library.
>         rvm (Libs)  -- A "recoverable virtual memory" library that allows
>                                persistant memory based data structures with a
>                                transaction system for consistency in the face of crashes.
>         rpc2 (Libs) -- A remote procedure call package used by Coda 
>                                (depends on lwp)
>         codafsd(net) --    The Coda "file system driver", the kernel module
>                                required to make Coda work.
>         coda (net) -- Coda binaries including venus, the client cache manager,
>                               and vice, the coda server.   This package would do a 
>                               standard setup for client.   Would require knowledge and
>                               work to finish building a Coda server.  (depends on lwp,
>                               rvm, rpc2, and coda-fsd.)
> 
> 
>        This would require the coda-fsd for a server.    Coda servers do not
> need the codafsd.   An alternate package list could be lwp, rvm, rpc2,
> codafsd and then split coda into:
>         coda-client (net) -- The client binaries.
>         coda-server (net) -- The server binaries.
> 
>         The problem with this is that both server and client are compiled from
> the same source tree.  It would make the coda-client and coda-server 
> packages have the same source tar file and the source tar file
> would not be called either coda-client nor coda-server but just coda.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Phil Nelson | 5 Sep 2007 07:19
Picon

Re: [itp] Coda filesystem

On Tuesday 04 September 2007 10:08:52 pm Reini Urban wrote:
> Should I prepare some cygport and hint files for you?

I would appreciate that.  Thanks.

--Phil

--

-- 
Phil Nelson (phil at cs.wwu.edu) http://www.cs.wwu.edu/nelson
NetBSD: http://www.NetBSD.org  Coda: http://www.coda.cs.cmu.edu
Permalink | Reply | 0 comments |
headers
Warren Young | 5 Sep 2007 23:46
Favicon

Test and upload: ctags 5.7

Package files:

	http://tangentsoft.net/cygwin/ctags-5.7-1-src.tar.bz2			 
http://tangentsoft.net/cygwin/ctags-5.7-1.tar.bz2

This just reflects the release of a new upstream version.

Although I've been the ctags maintainer for nearly two years, this is 
only my second package submission due to the long release cycle, so 
please check it.  It built without problems, but I'm still a newbie at 
this, so what do I know?

I did see the discussion about etags after the Emacs 22 packages were 
released, but the consensus in the thread seemed to be that no change 
was necessary.  Consequently, these packages were made the same way as 
the 5.6 ones were.  If that's not okay, let's discuss.
Permalink | Reply | 5 comments |
headers
Jari Aalto | 6 Sep 2007 13:01
Favicon
Gravatar

Re: Test and upload: ctags 5.7

* Wed 2007-09-05 Warren Young <warren-qKybWrIjVgNBDgjK7y7TUQ AT public.gmane.org>
* Message-Id: 46DF239C.40205 AT etr-usa.com
> Package files:
>
> 	http://tangentsoft.net/cygwin/ctags-5.7-1-src.tar.bz2
> http://tangentsoft.net/cygwin/ctags-5.7-1.tar.bz2

Web server problem?
Jari

1)
    wget http://tangentsoft.net/cygwin/ctags-5.7-1-src.tar.bz2
    --14:00:22--  http://tangentsoft.net/cygwin/ctags-5.7-1-src.tar.bz2
               => `ctags-5.7-1-src.tar.bz2'
    Resolving tangentsoft.net... 209.216.249.168
    Connecting to tangentsoft.net|209.216.249.168|:80... connected.
    HTTP request sent, awaiting response... 302 Found
    Location: http://tangentsoft.net/missing.html [following]
    --14:00:24--  http://tangentsoft.net/missing.html
               => `missing.html'
    Connecting to tangentsoft.net|209.216.249.168|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 3,795 (3.7K) [text/html]

    100%[====================================>] 3,795         22.60K/s             

    14:00:25 (22.50 KB/s) - `missing.html' saved [3795/3795]

2)
    ...
(Continue reading)

Permalink | Reply | 4 comments |

Gmane