From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7956 invoked by alias); 10 Jan 2014 15:07:31 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 7940 invoked by uid 89); 10 Jan 2014 15:07:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.6 required=5.0 tests=AWL,BAYES_40 autolearn=ham version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 10 Jan 2014 15:07:28 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 166B51A0C36; Fri, 10 Jan 2014 16:07:26 +0100 (CET) Date: Fri, 10 Jan 2014 15:07:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Bringing up NFS server on 64 bits Message-ID: <20140110150726.GH10296@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <001701cf0e08$e399abe0$aacd03a0$%fedin@samsung.com> <20140110135208.GG10296@calimero.vinschen.de> <002301cf0e10$6c1ed7e0$445c87a0$%fedin@samsung.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SNIs70sCzqvszXB4" Content-Disposition: inline In-Reply-To: <002301cf0e10$6c1ed7e0$445c87a0$%fedin@samsung.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2014-01/txt/msg00074.txt.bz2 --SNIs70sCzqvszXB4 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1414 On Jan 10 18:29, Pavel Fedin wrote: > Hello! >=20 > > Thanks for working on that. It's highly appreciated. Did you already > > make yourself familiar with Cygwin package maintainance(*)? >=20 > Yes, i did. However, perhaps you'll call me a bad guy, but the answer to= the first question: >=20 > * Do you have the time to maintain the package? >=20 > is "sorry, but likely no". We can't take the packages if you're not willing to maintain them. We already have enough packages where the maintainers disappeared. > I happen to have time only episodically. What obligations does this put o= n me exactly ? For example, does this mean that i must keep the package up = to date and sync up with the mainstream ? Not necessarily. If the package is in a good shape, has no known security issues, and works fine with the latest Cygwin, you're good. Other than that, just keep an eye on the Cygwin ML if somebody reported a problem with your packages and see if you can lend a hand, maybe. This is a generic problem. Maintaining packages does not actually cost a lot of time, unless you're trying to stick to the bleeding edge or try to maintain too many packages. But people still shy away from that without even trying. That's pretty disappointing. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --SNIs70sCzqvszXB4 Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJS0AytAAoJEPU2Bp2uRE+g5A0QAIP2n4NvLT2T5G7KwWQcerf8 dP1+77rljyScT5stsF5DORQQMMrh8JznO9y8XzIkdGvYt8NMILEup3SbEG2tc0K1 Rr02EzgQTQILfxzM1T+TPOZ6QQcBJ2ohcUdNLgZtVNAw1N0woHxnONUyJgtGzPiE cU+5i09u6lYq6e+Ck/1mX/SCHoSor+V5+fZUQYeRkT0EQdK+8whRudi401bUYzLx jsFboGqLBN1kzY09ntJ/9IUUe4TTyr2xlTD9hm96Lbg1ey7gic0ypVhXNe1AaU36 +TmH9hZ1uXNfD4nn34w2R+OPgOysDHzllpjnCpm3wWfs3mN6AERvrmdU3U3/rIN/ +JjyuTDQbS3WVR7Fab9JoVBgoIqUFC+NN7P8jbN2iO+w5ID1jS1N2f8xgANMd6kR 84RwVgeUgz8dVC5bhdZi4x6vjZnk/vKfgQEc0iO/fmkeMJqGpAu1AoxT1qWRYEcb VWSTz0TuLlDrisKNYDA86xmiO6XwBf4i42Bm8ze/DnrY4AV068dzpuXLEYs0VL1c M3JmE2hLzpQROJxw5YnWgzLwiYIe87uxC9gGyeN07qBJb+lSl2NDhd8f0TxZHRs7 EJJn0IdSn2EhKRTrtRXsWnb2KA2EJykpUqI8Guzp0IEx/wnV1tw2qYHxQ5ozMYFZ 62Gjm90n580dP6jceL7Y =ZD1F -----END PGP SIGNATURE----- --SNIs70sCzqvszXB4--