From owner-freebsd-ports@FreeBSD.ORG Mon Feb 10 13:01:40 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2CBD79CE for ; Mon, 10 Feb 2014 13:01:40 +0000 (UTC) Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A19191AFB for ; Mon, 10 Feb 2014 13:01:39 +0000 (UTC) Received: by mail-la0-f45.google.com with SMTP id b8so4709825lan.18 for ; Mon, 10 Feb 2014 05:01:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=S5F8RzYaotRXeGtIk+KrRM28NxDaCBdo3vlgPJynZG0=; b=kOwupzZiYkMB+yMSojo9Y6MAp+TCogvuxyT9wGnH8XdUKIS11DMjCQ/Pa81Af/QxS5 A0O0aWO+P+nDKXQPa7w92/Q4zDGdWF//TA55eek/l2FdmG7wH1meMug2PV/8kxwvBC8b PTxrRTbupzZwXz5qn8xhrc1dTXFol/AWASiH0HP/EicsKzFvHUkECVLC3eSXnXDm6+PO IHMotypXtPRECZrXNzdsDse3hinF4dtlv+NSGJnSlTOD5eAf9q5zPWrL14Pa0QgOl5mD Z2kom5zagtVN1g00XUcpCWAwyr9X9S2zvA9vTyIt1VH/IiFLZ8nYp2UA2ypehjtrxdzz YtUA== X-Received: by 10.152.28.200 with SMTP id d8mr638688lah.59.1392037297705; Mon, 10 Feb 2014 05:01:37 -0800 (PST) Received: from [192.168.77.101] (mail1.amcu.gov.ua. [213.160.139.2]) by mx.google.com with ESMTPSA id dm8sm22207977lad.7.2014.02.10.05.01.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Feb 2014 05:01:36 -0800 (PST) Message-ID: <52F8CDAE.2090109@gmail.com> Date: Mon, 10 Feb 2014 15:01:34 +0200 From: Kozlov Sergey User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re-inventing the FreeSWITCH port Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 13:01:40 -0000 Hi everyone. I'm working on re-inventing the FreeSWITCH port. The previous FreeSWITCH port was deleted not so long ago and the current -devel variant is outdated. I've already ported and patched some relatively simple ports, but FreeSWITCH is completely different case. The software consists of the core (which is pretty useless alone) and 151 modules which add functionality to the core, 45 of which are considered the default packaging. The main questions are: 1. What architecture is the best for this kind of port? The options are: a. Create one freeswitch-core port, 151 freeswitch-mod_foobar ports and a freeswitch metaport which will bring in the core and all the modules from the default packaging? b. Create one freeswitch port with 151+ options and default packaging modules declared as default options c. Option (b) with the freeswitch-full MASTERDIR port which installs all the modules d. Your option 2. When should I post the first version of the port? The thing is that every module needs it's own distfiles, dependencies, patches, plist entries and so on. Every module needs as much effort as a small port, and thoughts that i need to properly write options, patches, plist entries and everything else for 151 modules drive me crazy. Now I've managed to correctly build the default packaging. If I used option (b) from the first question then I could create the freeswitch port without options, a static plist and post it right away, making all the changes afterwards. This will create a freeswitch binary package which will be ready to use and won't change much later. 3. Testing the port. The complexity of this port makes me think it will be full of build errors, which will produce suboptimal or broken binaries. How to ask to consider this port experimental? Should I only write the warning message in pkg-message or maybe something else? Any help is greatly appreciated. Best regards, Kozlov Sergey.