cvs commit: ports/editors/openoffice-2.0-devel Makefile
Makefile.localized oo_setup.resp openoffice-wrapper
kris at obsecurity.org
Sun Jun 13 18:22:50 PDT 2004
On Mon, Jun 14, 2004 at 09:47:41AM +0900, Nakata Maho wrote:
> In Message-ID: <20040614001431.GA75296 at xor.obsecurity.org>
> Kris Kennaway <kris at obsecurity.org> wrote:
> Thank you very much for your feedback!
> > Have they finally fixed localized builds so they don't compile the
> > entire OO package suite? This is a major headache for package
> > building since
> This is also my concern. For localized builds, we can build all
> the localized version at one time, just adding ALL in configure_args.
> however current situation of ports framework, it is quite difficult.
> > * The OpenOffice 1.1 builds are not deterministic; they often fail
> > with internal errors in random places.
> Hmmm...I haven't encounter such situation for FreeBSD 5.2.1-RELEASE.
> I restrict supported environment to FreeBSD 5.2.1-RELEASE
> so that others can build smoothly. is it better for us to
> restrict FreeBSD version? or does it occur
> even for FreeBSD 5.2.1-RELEASE?
I don't know since I only build packages against the head of the
branches. I've forwarded some of the logs to openoffice@ over the
past few months, though.
> > > 4) make use of ccache
> > Is this a help within one build, or only useful for repeated builds.
> > I'm concerned it will have a significant space impact on package
> > builds without benefit.
> It doesn't help for one build. ONLY useful for repeated builds.
OK, I think it should be disabled for the PARALLEL_PACKAGE_BUILD case.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-all/attachments/20040613/8a918a02/attachment.bin
More information about the cvs-all