with the cvs history? trying to help INDEX builds.
Chris Rees
utisoft at gmail.com
Fri Jan 20 09:18:47 UTC 2012
On 19 Jan 2012 08:58, "Matthew Seaman" <m.seaman at infracaninophile.co.uk>
wrote:
>
> On 19/01/2012 01:31, Michael Scheidell wrote:
> > in manually trying to build an index for a tinderbox/binary/portmaster
> > distribution, I started to look at some of the things that slow these
down.
> >
> > and, being a former real-time, robotics guy... I figure, take ONE line
> > of code out, and you make things faster.
> >
> > anyway, worth the cycles?
> > take out -.include <bsd.port.pre.mk>; -.if ${ARCH} == "sparc64"
> > -BROKEN= Does not install on sparc64
> > -.endif
> > and replace it with NOT_FOR_ARCHS= sparc64 ?
> > without bsd.port.PRE, you won't (try) to pull in lots of other things,
> > optional things (options,perl, mysql, etc)
> >
> > worth the cvs history cycles to do this?
>
> I'd say worth it to standardize on NOT_FOR_ARCHS / ONLY_FOR_ARCHS to
> handle this sort of thing. By my calculations there are 28 ports that
> set 'BROKEN' because of architecture incompatibility on my amd64
> system[*], whereas there are 904 ports that set either ONLY_FOR_ARCHS or
> NOT_FOR_ARCHS.
>
> Cheers,
>
> Matthew
>
> [*] there would be more on sparc64 or other tier-2 architectures, but
> the way I counted didn't pick those cases up, just the ones that set
> BROKEN on the current architecture.
>
> portindex=> SELECT
> p.parent || '/' || p.name as port
> FROM
> caveat NATURAL JOIN ports_by_name p
> WHERE
> caveat_type='BROKEN'
> AND caveat ~ 'sparc|i386|amd64|ia64|pc'
> ORDER BY
> port
> ;
> port
> --------------------
> devel/ruby-avl
> devel/ustl
> games/xbloody
> graphics/gmt
> graphics/ruby-tgif
> irc/eggdrop
> japanese/ne
> lang/oorexx
> lang/py-prolog
> lang/qscheme
> lang/rscheme
> lang/scsh
> lang/sr
> math/matrix
> net-im/gyach
> net-mgmt/docsis
> net/cnet
> net/hawknl-devel
> net/ngrep-lib
> net/py-libnet
> net/tridiavnc
> science/elmerpost
> sysutils/freecolor
> sysutils/hpacucli
> textproc/coco
> textproc/rtfx
> x11-toolkits/fox17
> x11/decurs
> (28 rows)
>
No, it's not worth it :)
This means we won't be able to differentiate between BROKEN and IGNORE.
Chris
More information about the freebsd-ports
mailing list