Commit Graph

13 Commits

Author SHA1 Message Date
jasper
1419a22726 - update to vte-0.34.2 2012-11-13 08:24:52 +00:00
jasper
25ef599e04 - update to vte-0.34.1 2012-10-16 08:34:14 +00:00
jasper
831b895a62 - update to 0.34.0 2012-09-17 08:05:04 +00:00
ajacoutot
bfa789b82c Update to vte3-0.32.0. 2012-03-23 13:25:00 +00:00
ajacoutot
c78896072c Sync with mpi@ patches from upstream. 2012-03-09 06:45:16 +00:00
mpi
60973badf6 Make use of openpty(3) to allocate a pseudo-tty instead of the
gnome-pty-helper.

ok ajacoutot@, landry@
2012-02-24 10:44:55 +00:00
espie
5ee810f609 update fix: vte2 should *not* update to vte3.
parts of gnome want vte3, and yet some other stuff (py-vte) still wants vte2.
if we let vte2->vte3 because of gnome, then py-vte will complain, and the
update won't happen.

considering we've set things up so vte2 and vte3 can coexist, the thing to do
is have vte2 update to vte2-newer, let gnome3 pick and install vte3 as well,
keeping py-vte happy and ending with a fully updated machine.

On the way, need to tell quirks AND vte about vte-pyhelper, which vanished
into vte2/vte3 (and again, pick one).

(triggers a bug in pkg_add caching which requires -current, btw ;( )

Solves update issue reported by Mikolaj.

Ports STILL fully locked, this making it in as a vital update thing,
(no don't ask, your silly little update won't make it)

okayed by naddy@
2012-02-06 22:07:09 +00:00
landry
6eb752069d Add @pkgpath devel/vte,-pty-helper to allow seamless updates from
a september pkg snapshot, bump REVISION.
ok ajacoutot@
2011-12-21 15:47:45 +00:00
ajacoutot
dc4f6bf048 It seems the @conflict marker format changed... 2011-10-02 16:11:11 +00:00
jasper
d6afa123c7 fix the other conflict marker too.. 2011-09-26 15:17:25 +00:00
ajacoutot
98afa6b86e Fix conflict marker. 2011-09-26 15:10:34 +00:00
jasper
b216479d54 missing conflict marker 2011-09-26 14:41:57 +00:00
jasper
d026e5f5ae import vte 0.30.0 (gtk3 only) 2011-09-26 14:31:33 +00:00