Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <3A19AB12.12A54C79@t-online.de> Date: Mon, 20 Nov 2000 23:52:02 +0100 From: michael-ring AT t-online DOT de (Michael Ring) X-Mailer: Mozilla 4.75 [de] (Windows NT 5.0; U) X-Accept-Language: de MIME-Version: 1.0 To: cygwin-apps AT sources DOT redhat DOT com Subject: Re: Set up a cygwin-apps CVS repository? References: <3A19A7F9 DOT 13521 DOT 1C10D985 AT localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 320032306730-0001 AT t-dialin DOT net > < Set up a cygwin-apps CVS repository? > > > > Would it help if I set up a repository for cygwin-apps so that people > > could keep everything in a central location? > > > I also like the idea, as long as the sources somehow keep in sync with the 'real' software-distributions. Perhaps a repository with rpm-specs and patches to original software would be better, this makes it easier to update software if a new release of the original software hits the road. build scripts et al are already done for rpm and are proven to work very well, so setting up something this way should be easy. (Well, as soon as a working perl hit's the road...) Till then, Michael Ring