Re: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing

[Christopher Faylor <cgf at redhat dot com>]

On Fri, Apr 19, 2002 at 04:55:57PM -0400, Harold Hunt wrote:
>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 had the same thoughts and hoped you'd have a brilliant solution.  :-)

>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.

Hmm.  Yes.  I think this would work.  That might be the best solution.

In fact, it may be a nice trend setter.

>
>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?

 From my "generate a package" script:

find $package_src/* -print -follow | egrep -v '\.cvsignore|\.bak$|\.orig$|~$|^.#|CVS|%redact|/tags$' | egrep -v "$src_exclude" |
 sort | tar -T - --no-recursion -cjf "$tarstem"-src.tar.bz2

cgf