Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Mar 2013 15:50:58 +0600
From:      Muhammad Moinur Rahman <5u623l20@gmail.com>
To:        Ruslan Makhmatkhanov <cvs-src@yandex.ru>
Cc:        FreeBSD Ports <freebsd-ports@freebsd.org>, frank <frank@dynamical-systems.org>
Subject:   Re: ports/175104: [PATCH] net/libosip: update to 4.0.0
Message-ID:  <CA%2BnPUkyCPx_BcgXmtD%2BWY4dg_e4SKanaD9rjZ5pAZSakKs9KbA@mail.gmail.com>
In-Reply-To: <515011F5.8050101@yandex.ru>
References:  <CA%2BnPUkzxmb=tMkQYrOsmfL-71gM_puhnwEvUighsvAXks9SwAA@mail.gmail.com> <514F40E4.6060208@yandex.ru> <514F426A.9090108@yandex.ru> <CA%2BnPUkx3O53efbciXjqNAjnT0W=54LQPQ8h9hf61%2BqWdVJBj9g@mail.gmail.com> <515011F5.8050101@yandex.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks Ruslan. I think we need to modify the siproxd and libexosip too. But
I have got a new patch for libexosip too. Should I create a patch for it or
wait for libosip to complete?

Regards,
Muhammad


On Mon, Mar 25, 2013 at 2:59 PM, Ruslan Makhmatkhanov <cvs-src@yandex.ru>wrote:

> Muhammad Moinur Rahman wrote on 24.03.2013 23:08:
>
>  Hi Ruslan,
>>
>> Do we need to do it in a REPOCOPY style? Or plain simple new port?
>>
>> Regards,
>> Muhammad
>>
>
> Yes, net/libosip will be svn cp'ed to net/libosip24 and then your patch
> applied to it (with you as maintainer). I'll try to do that later this day.
>
>
>>
>> On Mon, Mar 25, 2013 at 12:14 AM, Ruslan Makhmatkhanov <cvs-src@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>;
>>>> <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<http://siproxd.sourceforge.net/index.php?op=relnotes>;
>>> >
>>>
>>
>
>
> --
> Regards,
> Ruslan
>
> Tinderboxing kills... the drives.
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BnPUkyCPx_BcgXmtD%2BWY4dg_e4SKanaD9rjZ5pAZSakKs9KbA>