This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Recent cygport and cygwin-specific READMEs [Was: Re: GCC-4.7.2-2: Go/No-go?]
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 11 Apr 2013 18:52:01 +0200
- Subject: Re: Recent cygport and cygwin-specific READMEs [Was: Re: GCC-4.7.2-2: Go/No-go?]
- References: <51643F10 dot 7000905 at gmail dot com> <87eheixuz8 dot fsf at Rainer dot invalid> <20130410154730 dot GA404 at ednor dot casa dot cgf dot cx> <516599BE dot 7090000 at gmail dot com> <51661EA2 dot 1070801 at users dot sourceforge dot net> <51665212 dot 6050101 at gmail dot com> <51665F0F dot 8040902 at users dot sourceforge dot net> <5166AE89 dot 2050704 at cwilson dot fastmail dot fm>
While the mirror script pulls down the shiny new gcc from Daveâ
Charles Wilson writes:
> #1) Is it possible to also record cygwin-specific README content
> within the cygport(5)? [1] If so, can you do more than one? (I'm
> thinking here of inetutils, which has a separate cygwin-specific
> README for the -server (sub)package and for the -client (sub)package).
Here scripts (cat > file <<EOF) would work, I've been using that to drop
some few-line-long script in-place into the build once. I don't think
it would necessarily work well for the README files, but I guess it's
possible to append them to SRC_URI (you'd have to move them to the
CYGWIN_PATCHES directory, though). If it's just the fact that editing a
patch file is ugly, then you could do something along the lines of "diff
-u /dev/null package.README > package.README.patch" and then add
package.README.patch to the PATCH_URI. But maybe Yaakov could consider
something like README_URI instead (I think I could provide a patch to
that effect).
> #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, look at the recent packages for gmp/mpfr etc.
> #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?
I try to add both the requisite require lines to the *-devel package and
a depend line in the cygport file.
HTH,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada