Re: [ITA] mpfr (libmpfr-devel / libmpfr4)

["Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>]

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