Am Donnerstag, 15. Dezember 2011, 10:09:36 schrieb
Alexander Graf:
> On 15.12.2011, at 09:58, Michal Vyskocil <mvyskocil(a)suse.cz> wrote:
> > On Wed, Dec 14, 2011 at 05:00:08PM +0100, Adrian Schröter wrote:
> >> Am Mittwoch, 14. Dezember 2011, 13:58:43 schrieb Michal Vyskocil:
> >>> On Wed, Dec 14, 2011 at 01:34:54PM +0100, Dirk Müller wrote:
> >>>> Hi,
> >>
> >>>
Hallo Dirk,
> >
> >> ...
> >
>
>>>> which finishes building javadocs target successfully after a
> >>>> chewing for 160 minutes under qemu (53 minutes on native
> >>>> hardware).
> >>>
>
>>>> Currently I went for this solution (patch is only applied on
> >>>> %arm), any comments, ideas appreciated. I guess it would help
> >>>> overall build speed by only building "ant jars " and
maybe "ant
> >>>> test-jars" and not also javadocs?
> >>
> >>> I
vote for exclude ant-javadoc (.*-javadoc (?) even that is not so
> >>> easy) build at all on %arm. Reasons are
> >>
> >>> *
arm is now built in qemu using interpreted java, which is slow^2
> >>> than
> >>
> >>>
on other arches
> >
> >> well,
we (esp. Alex) worked on improving it. It is not as horrible as
> >> it was.>
> >>> *
we already have ant-javadoc built well on i586/x86_64 so this
> >>> won't
> >>
> >>>
add us anything new
> >>
> >>> *
as there are no dependencies on javadoc packages, there won't be
> >>> any
> >>
> >>>
problems with excluding
> >>
> >>>
Adrian, what would you say? As far I remember, you are not so happy
> >>> with that approach.
> >
> >> Hm, I
have no opinion. If you don't need to fix/update documentation
> >> according to our distro (or package configuration) it is pointless to
> >> re-generate.
> > OK, then
I have submitted a fixed ant package to Factory - request 96712
>
> > * changed distribution ant target to
dist
> > * make javadoc target really configurable
> > * disable it on %{arm}
> That means that on openSUSE:Factory:ARM
we'll be missing the documentation
> noarch packages, because it's not built in the same repo as x86, right?
Frankly I see no reason to have javadoc package on arm as this is
mostly not the best machine for development of Java programmes. In fact
I see no reason for -javadoc packages at all, as everyone use google ant
javadoc and read it on the web.
Yes. Even when it would build in the same repo, it would not be available on
arm during build time though (except we define export filters).
I hope there are no packages with build require it.
Quick find . -name '*spec' | xargs grep 'BuildRequires.*ant-javadoc'
returned me nothing, so no build errors on arm are expected.
Regards
Michal Vyskocil