Yet another INDEX builder.

Peter Jeremy peterjeremy at
Fri Sep 29 13:14:32 PDT 2006

On Fri, 2006-Sep-29 19:21:22 +0200, Michel Talon wrote:
>timings (*) one gets. On my machine, a P4 3Ghz, oldish, it takes 23 minutes to
>complete building the INDEX, but the python script doesn't run more than 1
>minute. Everything else is IO, i think. So one cannot expect any performance
>improvement by writing such a program in C.

IMHO, the advantage of using C is that it would remove the need for
yet another interpreter to be installed to manage my ports.  Or, to
put is another way, by writing it in python, you have made your script
less attractive to me than it would be if it was in C/sh/awk.

Several years ago, the Project went to a lot of effort to re-writes
bits of the base system in C/sh/awk to allow perl to be removed.
Ports-based maintenance tools are (of course) free to use any language
but the proliferation of different tools using different languages
means that I wind up with a large number of languages and interpreters
installed just to easily manage my system:
- CVSup needs Modula-2
- portupgrade needs Ruby
- your new index builder needs Python
- various other ports management tools use perl

Please don't take the above as a personal attack - I'm merely pointing
out that there are other reasons apart from performance for using C.

Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the freebsd-ports mailing list