Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
From: "Harold Hunt" <huntharo AT msu DOT edu>
To: <cygwin-apps AT cygwin DOT com>, <cygwin-xfree AT cygwin DOT com>
Subject: RE: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
Date: Fri, 19 Apr 2002 16:55:57 -0400
Message-ID: <NHEELHJHHFKPMAEAFMFCIEBJCNAA.huntharo@msu.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
In-Reply-To: <20020419171504.GA23436@redhat.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

Chris,

> It's up there.  Should be on mirrors shortly.

Very cool.

> One thing I just noticed, though (by looking at
> http://cygwin.com/packages/), was that the source tar.bz2 files don't
> seem to be part of this.  There should probably be fewer source tar
> balls than binary but they should be part of the distribution, right?
> If not, we'll inevitably get questions.

I've thought about this enough to make my head spin.  The only real solution
I could come up with is to tell folks to go to the XFree86 CVS tree.

The main problem with -src packages for us is that almost nothing will
change after an XFree86 release except for the xc/programs/Xserver/hw/xwin
directory, where I make modifications to the XWin server.  So, what do I do
for packaging?  Which of the XFree86-* packages do I include source with?
Do I include one huge tarball with everything and another small tarball that
has just the hw/xwin directory so that it can be easily updated?  I'm
confused.

I didn't quite gather from the earlier discussions whether we can have a
source package seperate from any binary packages.  i.e., could we have
XFree86-full-src without an associated binary package?  Or would we have to
make XFree86-base-src the package that contained the full source archive.


In a related question that has to do with my laziness, I need a way to
tarball a CVS tree without including the CVS directories.  I'm sure this can
be done with a simple script, but I'm a programmer not a script writer.
Anyone want to point me to an existing script that does this, or write one
for me?


Later,

Harold

> -----Original Message-----
> From: cygwin-xfree-owner AT cygwin DOT com
> [mailto:cygwin-xfree-owner AT cygwin DOT com]On Behalf Of Christopher Faylor
> Sent: Friday, April 19, 2002 1:15 PM
> To: cygwin-xfree AT cygwin DOT com; cygwin-apps AT cygwin DOT com
> Subject: Re: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available
> for comments and testing
>
>
> On Fri, Apr 19, 2002 at 12:52:27PM -0400, Christopher Faylor wrote:
> >On Fri, Apr 19, 2002 at 01:24:48AM -0400, Harold Hunt wrote:
> >>Chris,
> >>
> >>> Shall we add this to the cygwin distro or are we still waiting for
> >>> some postinstall shell script work?
> >>
> >>These will forever be known as Harold's Famous Last Words:
> >>	Sure Chris, why not?  Go ahead and add the packages to the distro.
> >>
> >>Be aware, I just updated XFree86-xserv to 4.2.0-2, so you'll
> need to grab
> >>the latest packages off of ftp://huntharo-4.user.msu.edu/pub/cygwin/
> >>
> >>That's all for now.
> >>
> >>I can't wait to see how many people use Cygwin/XFree86 now!
> >
> >Ditto.  Hope you're ready for this.
>
> It's up there.  Should be on mirrors shortly.
>
> One thing I just noticed, though (by looking at
> http://cygwin.com/packages/), was that the source tar.bz2 files don't
> seem to be part of this.  There should probably be fewer source tar
> balls than binary but they should be part of the distribution, right?
> If not, we'll inevitably get questions.
>
> cgf