This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [ITA] mpfr (libmpfr-devel / libmpfr4)
- From: "Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 10 Apr 2013 21:38:43 -0500
- Subject: Re: [ITA] mpfr (libmpfr-devel / libmpfr4)
- References: <87r4jnmfa6 dot fsf at Rainer dot invalid> <87sj39t0ku dot fsf at Rainer dot invalid> <516533B9 dot 9070503 at users dot sourceforge dot net> <87ip3uxv5x dot fsf at Rainer dot invalid>
On 2013-04-10 10:27, Achim Gratz wrote:
Yaakov (Cygwin/X) writes:
Also, automating the patches is possible, e.g.:
PATCH_URI=$(seq -f http://www.mpfr.org/mpfr-${VERSION}/patch%02.0f 1 3)
Then use the '3' to control the number of patches available.
The problem wasn't really downloading the patches. The patch format
does not apply with the options that cygport tries, so you'll have to
apply it manually still.
Only 'allpatches' doesn't apply; the individual ones do sequentially.
Question: Currently the documentation goes into the umbrella package.
Would it make sense to keep that package empty and have a separate doc
package. If yes, I'm leaning towards naming it libmpfr-doc rather than
mpfr-doc, but there doesn't seem to be a clear naming convention judging
from the existing packages.
Unfortunately we don't have consistent naming convention, but a -doc
package would be preferred IMO.
Yaakov