HEADS UP: GNOME 2.20.1 available for FreeBSD

Jeremy Messenger mezz7 at cox.net
Thu Oct 25 13:04:25 PDT 2007

On Thu, 25 Oct 2007 14:22:32 -0500, <tmclaugh at sdf.lonestar.org> wrote:

>> On Thu, Oct 25, 2007 at 12:45:44AM -0400, Joe Marcus Clarke wrote:
>>> On Thu, 2007-10-25 at 00:37 -0400, Aryeh M. Friedman wrote:
>>> > > <snip>
>>> > > You will have to talk to the mono maintainer as we didn't touch
>>> > > lang/mono port at all.
>>> >
>>> > Not to be pushy but since gnome is one the most commonly installed
>>> ports
>>> > and mono is a required component shouldn't the responibility to make
>>> > sure that all dependancies (even ones that are not your problem
>>> > directly) build correctly?
> I keep two personal machines at home for FreeBSD work.  One running 7 and
> one running 6 (currently down due to disk failure) and both have a
> tinderbox along with multiple jails on them.  RELENG_7 only branched
> recently so I haven't even had much time to setup a FreeBSD 8 system.   
> I'm
> not sure I will even have a FreeBSD 8 system anytime soon.  I have no  
> more
> free PCs at home and already need to purchase a new Linux box which I  
> keep
> as a reference machine.  I can scrap the FreeBSD 6 box and load FreeBSD 8
> which I have thought about but that has its own issues.  Do I drop  
> testing
> on what will become a legacy branch soon even though it is still widely
> used?  Mono's issues on FreeBSD have historically been thread related so
> do I want to drop the last branch with libpthread?
> If something breaks on a development branch it will get fixed but
> typically at a slower rate.  My personal opinion is my resources are
> better spent making sure ports work on production branches rather than a
> development branch.  People should expect breakage in a development
> branch.  They should be able to expect things work and have been
> reasonably tested when using a production branch.
>>> We did a lot to verify GNOME builds correctly.  Our tests were done
>>> mainly on 6.X and 7.X (as 8.X is still a fairly new version).  Since
>>> you're running bleeding edge code, you may run into problems.  You need
>>> to report problems to the proper maintainers, and be patient.
>> Mono has an 8.x problem as well.  I sent this patch to the maintainer
>> yesterday.  It works for me, but I haven't heard back.   Folks running
>> mono on -CURRENT are welcome to try it.
>> --
>> Ted Faber
>> http://www.isi.edu/~faber           PGP:
>> http://www.isi.edu/~faber/pubkeys.asc
>> Unexpected attachment on this mail? See
>> http://www.isi.edu/~faber/FAQ.html#SIG
> Just committed the fix.  Thanks Ted.

I haven't look at configure, so wondering how about do something like this?

if ${OSVERSION} >= 700000
	@${REINPLACE_CMD} -e 's|freebsd6|freebsd*|g' \
		${WRKSRC}/configure ${WRKSRC}/libgc/configure

If 6, 7 and 8 are same then a wildcard should take care of future version  
of FreeBSD to save your headache.


> tom

mezz7 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team  -  FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org
http://wiki.freebsd.org/multimedia  -  multimedia at FreeBSD.org

More information about the freebsd-ports mailing list