Mail Archives: cygwin/2000/12/17/23:52:51
On 17 Dec 2000, at 21:31, Chris Abbey wrote:
> At 18:46 12/17/00 -0800, Stephen C. Biggs wrote:
> >A clarification on source format:
> >If I upload the source tarball, do I just upload my patches or do I
> >upload the source directory that I used after my patches are
> >applied? If so, how do I provide the patches as part of the
> >distribution? That is, if there is already a patched source directory,
> >then the patches are redundant.
>
> see the faq entry: http://cygwin.com/faq/faq.html#SEC76
> which refers to: http://cygwin.com/ml/cygwin-apps/2000-11/msg00055.html
> which answers your question.
Thank you for the reply. This does NOT entirely answer my question.
Step 7. modify the top level makefile to install
CYGWIN-PATCHES/tex-4.0.README into /usr/doc/Cygwin/
How do I do this?
Also, looking in ftp://ftp.franken.de/pub/win32/develop/gnuwin32/incoming, I
see files *.cygwin.BUILDLOG.gz, *.cygwin.PATCH.gz, *.cygwin.README,
*.cygwin.tar.gz, and *.src.tar.gz.
Everything I understand except for the *.src.tar.gz. Is this the patched or
the unpatched vanilla version of the source tarball?
The web page says:
"Now, you've got
tex-4.0-1-src.tar.gz
the pre-patched, cygwin-specific source
code for the package"
How can it be pre-patched and ALSO cygwin-specific??
>
>
> now the forces of openness
> have a powerful and
> unexpected new ally
> http://ibm.com/linux/
>
>
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -