From: "Philip Brown" <pbrown00@earthlink.net>
To: <cygwin@cygwin.com>
Subject: Anomalies in Source Distributions
Date: Thu, 22 Apr 2004 17:27:00 -0000 [thread overview]
Message-ID: <E1BGhh4-0003aF-00@turkey.mail.pas.earthlink.net> (raw)
For whatever it's worth, I've come across the following anomalies which look
like very minor configuration control bugs in the Cygwin source
distributions (but what do I know ;-)
patchutils-0.2.22-2.src.tar.bz2 - There appears to be a configuration
control problem. If you expand the source, it is located in a directory
called patchutils-0.2.22-1, instead of -2.
textutils-2.0.21-1.src.tar.bz2 - Similar to above. Expand the source and
the directory is named textutils-2.0.21 instead of textutils-2.0.21-1.
cygutils-1.2.4-1.tar.bz2 - The doc files have 1.2.4 instead of 1.2.4-1 on
them in the .tar.bz2 file (due to .sh script). Specifically:
/usr/share/doc/cygutils-1.2.4/AUTHORS
/usr/share/doc/cygutils-1.2.4/BRANCHES
/usr/share/doc/cygutils-1.2.4/COPYING
/usr/share/doc/cygutils-1.2.4/HOW-TO-CONTRIBUTE
/usr/share/doc/cygutils-1.2.4/NEWS
/usr/share/doc/cygutils-1.2.4/PROGLIST
/usr/share/doc/cygutils-1.2.4/README
/usr/share/doc/cygutils-1.2.4/TODO
/usr/share/doc/Cygwin/cygutils-1.2.4.README
sharutils-4.2.1-3 - Similar to above for file:
/usr/share/doc/Cygwin/sharutils.README
which should be sharutils-4.2.1-3.README per your configuration system to
the best of my understanding.
--Phil Brown
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2004-04-22 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 17:27 Philip Brown [this message]
2004-04-22 18:02 ` Larry Hall
2004-04-27 20:48 ` Bas van Gompel
2004-04-28 1:11 ` Larry Hall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1BGhh4-0003aF-00@turkey.mail.pas.earthlink.net \
--to=pbrown00@earthlink.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).