On 4/11/2013 6:37 PM, Yaakov (Cygwin/X) wrote:
No, cygport(1) doesn't generate README content.
Too bad. Well, maintaining the READMEs in my local git repo
side-by-side with the cygport(5) is not that big a deal -- especially
with the other cygport(1) improvements, incl #3 below.
#2) Is it possible to use the auto-setup.hint-generator functionality
for multi-part package sets (e.g. which contain multiple separate
tarballs, in addition to -src and -debuginfo)? If so, how?
Yes; it just works
Fabulous.
#3) As I've been gone for a while, I might've missed recent changes: do
setup.exe and/or cygport support build dependencies directly in any way,
rather than the ad-hoc put-it-in-a-cygwin-README "technique" I've been
using 'til now?
See DEPEND in the cygport manual. (Yes, this is confusing now that
REQUIRES exists for additional *runtime* dependencies. I'm thinking of
renaming this to BUILDREQUIRES or the like, but for API compatibility
DEPEND would still work.) These are checked at the beginning of the
build step, and a warning issued if any are missing.
Great -- which actually means I can remove that bit from the
cygwin-specific READMEs. That's the most annoying part of keeping the
READMEs up-to-date anyway.
--
Chuck
