Hi Ruslan, Do we need to do it in a REPOCOPY style? Or plain simple new port?
Regards, Muhammad On Mon, Mar 25, 2013 at 12:14 AM, Ruslan Makhmatkhanov <cvs-...@yandex.ru>wrote: > Ruslan Makhmatkhanov wrote on 24.03.2013 22:07: > > Hi Muhammad, >> >> Muhammad Moinur Rahman wrote on 24.03.2013 17:41: >> >>> Hi, >>> Can anyone please take care of ports/175104? It has been a while and I >>> need >>> to update libexosip2, which is dependent on this. >>> >>> Regards, >>> Muhammad >>> >> >> net/siproxd fails to build with this version of libosip [1] (and builds >> fine with 3.6.0), so or this update should be coordinated with siproxd >> maintainer (cc:ed) or it should be added to the tree as libosip24 or >> something. The first one is preferred, because there is newer version of >> siproxd that may work with new libosip. >> >> [1] >> http://people.freebsd.org/~rm/**siproxd-0.7.2_3.log<http://people.freebsd.org/~rm/siproxd-0.7.2_3.log> >> > > Looks like the first one will fail because 0.8.1 also requires libosip2 > (3.x.x), according to release notes [1]. It may worth to check, but I'm > afraid it will be new port. > > [1] > http://siproxd.sourceforge.**net/index.php?op=relnotes<http://siproxd.sourceforge.net/index.php?op=relnotes> > > > -- > Regards, > Ruslan > > Tinderboxing kills... the drives. > _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
