Date: Wed, 29 Oct 2008 23:00:50 +1100 From: andrew clarke <mail@ozzmosis.com> To: Scot Hetzel <swhetzel@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: ports missing their packages. Message-ID: <20081029120050.GA77220@ozzmosis.com> In-Reply-To: <790a9fff0810290242m58012ac5r10bb761f65c97a1c@mail.gmail.com> References: <NBECLJEKGLBKHHFFANMBMECBCMAA.fbsd1@a1poweruser.com> <NBECLJEKGLBKHHFFANMBIEDJCMAA.fbsd1@a1poweruser.com> <790a9fff0810290242m58012ac5r10bb761f65c97a1c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed 2008-10-29 04:42:18 UTC-0500, Scot Hetzel (swhetzel@gmail.com) wrote: > So you are advocating that port maintainers have to create packages > for all the supported FreeBSD architecture's (amd64, arm, i386, ia64, > mips, pc98, powerpc, sparc64, sun4v). That would be 9 packages > needing to be created at the time the port maintainer submits the > upgrade PR. Or more if you want packages for both FreeBSD 6.x & 7.x. Presumably the 6.x series wlll be retired before 8.x is released... :) That brings up a question (not directed at you, Scot) - what is the usual procedure for port maintainers so they can test their ports on both 6.x & 7.x? In terms of building a port, is it a case of most porters running 7.x, and what compiles with gcc 4.2 without trouble is likely to be OK with gcc 3.4 also? I suppose you could install lang/gcc34 under 7.x and try building your port with that instead of the base gcc. Then it's just a matter of setting CC=gcc34. Or is there more to it than that?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081029120050.GA77220>