In <20060826212607.GA82729@troutmask.apl.washington.edu>, Steve Kargl <email@example.com> typed:
> On Sat, Aug 26, 2006 at 03:43:26PM -0400, Mike Meyer wrote:
> >>> Hmm. My copy of the port sets that for amd64 already. Checking the CVS
> >>> repository, it looks like a number of things have broken/unbroken in
> >>> the last few days. In particular, one of the repositories appears to
> >>> have a broken copy of the tarball the port is using. I'll update the
> >>> port, make distclean, and try again.
> >>> In the meantime, could you tell me which openoffice port you build?
> >>> I'm using openoffice.org-2.0, and not the -devel branch.
> >> pkg_info shows
> >> openoffice.org-2.0.3
> >> ls -l /usr/local/bin shows that I built the port on 7 Aug 06.
> >> Of course, the port could have been broken in the last 20 days. :(
> > Just out of curiosity, what are the chances of getting you to build a
> > package/tarball out of what you've built, since there isn't a package
> > availabe from the freebsd ftp sites? I'd be willing to make it
> > available for others to download.
> The chances are slim. I'm fairly certain that I deleted everything
> after the installation (ie., tarballs, build directories, dependencies).
> I'll check, but don't hold your breath. :(
For the archives. The openoffice.org-2.0 port just finished building
without a hitch on my 6-STABLE amd64 system. I couldn't find anything
when I went searchyng for such earlier. Hopefully this one will safe
people some time in the future.
I'll investigate the issue of multilib and multi-platform package
support, and possibly take it up in a more appropriate forum.
Mike Meyer <firstname.lastname@example.org> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.