Binary packages for releases and portupgrade

Martin Cracauer cracauer at
Wed Jan 6 20:17:57 UTC 2010

Peter Ulrich Kruppa wrote on Wed, Jan 06, 2010 at 08:46:38PM +0100: 
> On Wed, 6 Jan 2010, Martin Cracauer wrote:
> >
> >So the verdict is to hunt down OpenOffice packages manually and
> >install them so that portupgrade ignores them, then go from there.
> >
> >
> >seems to have what `portupgrade -P` should expect, right?
> >
> >So I wouldn't have to move from stable to release+sec.
> I wonder if people who succeed in building OOo (happens about 
> twice a year to me) could put their packages on some kind of ftp 
> server. From their mailing list I get the impression OOo-porting 
> team could need all kind of help.

Might be easier to just slam a Debian into a chroot.

How do chroot and Linuxulator play together, anyway? Can I have a
random-Linux in /compat/linux and then have a different one in 

Alternatively I could just leave this poor notebook alone WRT building
and run the same FreeBSD on one of my beefier machines to build binary
packages and share the successes.  Would probably involve two complete
installations, one with a ports tree that only ever builds OO (and
pulls in it's dependencies but nothing else).

Martin Cracauer <cracauer at>
FreeBSD - where you want to go, today.

More information about the freebsd-ports mailing list