Solaris 10 comes with libvte 0.11.11, which appears to be the minimum version that Terminal requires. However, while Terminal compiles against that version, it won't start and segfaults instead. Stack trace (uninformative): core 'core' of 9872: Terminal 080648c9 ???????? (8167040, 8161208, 0, 8164458) fd0d3e64 g_type_create_instance (81653b8, 8047760, 80476d8, 3, 24, fd0f6620) + 4d8 fd0bca98 g_object_constructor (81653b8, 0, 0, 0, 8164600, 0) + 20 fd0bbeda g_object_newv (81653b8, 0, 0, 50, 8084e60, 8) + 2c6 fd0bc994 g_object_new_valist (81653b8, 0, 8047958, 81653b8) + 290 fd0bca6e g_object_new (81653b8, 0, 80479a8, 805c562) + 5a 08064b6e terminal_screen_new (8090868, 140, 4, 0, 815d530, 809d098) + 16 0805c5bb terminal_app_open_window (8090860, 8088ea0, 80479d9, 805c39e) + 217 0805c8eb terminal_app_process (8090860, 80830d0, 4, 8047a0c) + 3b 0805bb7e main (1, 8047a3c, 8047a44) + 28e 0805b13c _start (1, 8047b3c, 0, 8047b45, 8047b9e, 8047bfc) + 80 Using the latest vte (0.20.5) works just fine, so either the Solaris libvte is just goofy or Terminal actually requires a newer version than 0.11.11. (This is more of an FYI. If the bug is in Solaris then no problem; if the truth is that Terminal does require a newer version of vte then it should check for that.)
The crash is not because there is missing api, so the dependency is just fine, but there are a few quirks in the older version of vte. Therefore (and new api additions) the new releases of terminal will require vte 0.17.1 or newer.
Closing, there is terminal version 0.4.0 now which depends on a recent version of vte.