From owner-freebsd-ports@FreeBSD.ORG Thu May 29 07:43:00 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5B716AAF for ; Thu, 29 May 2014 07:43:00 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 160D528C0 for ; Thu, 29 May 2014 07:42:59 +0000 (UTC) Received: from [192.168.0.21] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id BA15B438EB; Thu, 29 May 2014 02:42:41 -0500 (CDT) Message-ID: <5386E4E0.2030402@marino.st> Date: Thu, 29 May 2014 09:42:24 +0200 From: John Marino Reply-To: marino@freebsd.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Raghu HB , Michelle Sullivan Subject: Re: Creating new port References: <5385AFFA.7050206@sorbs.net> <5385B992.60202@sorbs.net> <5385C38A.1070400@sorbs.net> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports ML X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2014 07:43:00 -0000 On 5/29/2014 09:22, Raghu HB wrote: > Thanks Michelle for your time. > > Neither your answers nor the link provide the details which I am looking > for. The links you have been given do contain the detail that you are looking for. As far as "example" ports go, there are 25,000 of them. The bottom line is: if you found Michelle's suggestion unhelpful, nobody can help you I'm afraid. You're going to get the same answers repeatedly. John > > Thanks, > Raghu > > -----Original Message----- > From: Michelle Sullivan [mailto:michelle@sorbs.net] > Sent: Wednesday, May 28, 2014 4:38 PM > To: Raghu HB > Cc: FreeBSD Ports ML > Subject: Re: Creating new port > > Raghu HB wrote: >> Thanks Michelle, >> >> I copied the files in /usr/ports/sysutils/mrmonitor and ran the below >> commands I encountered the same issue. >> > > Ok for starters - you only copy the Makefile that you are making for the > port into there. >> root@:/usr/ports/sysutils/mrmonitor # make distinfo >> make: don't know how to make distinfo. Stop >> > This should not happen if you have a ports makefile there.. however it is > possible you have forgotten something (like making the last line: > .include ) > >> root@:/usr/ports/sysutils/mrmonitor # make makesum ===> Found saved >> configuration for mrmonitor-1.1 root@:/usr/ports/sysutils/mrmonitor # >> make package ===> Found saved configuration for mrmonitor-1.1 >> >> I need to understand below things which is not explained in hand book. >> >> 1. Detailed steps for creating new port >> > This is what you need: > http://www.freebsd.org/doc/en/books/porters-handbook/quick-porting.html#po > rting-makefile >> 2. Sample example for creating new port which nowhere available in the >> web >> > The link above provides a simple sample. >> 3. I have 10 files in a directory, I just need to create a package out >> of that and provide the package to customers they can install it. >> > You can't do that - you need to make the distribution into a tarball that > can be downloaded from a 'master site' >> 4. I do not have to build anything I just need to create the port for >> binaries. >> > > Yes, understood, do you have a makefile that will do this for you across > other platforms? >> >> I have searched enough in the web nowhere I found the answer... >> I think providing the files in tar format and script to deploy the >> files will be more easier than this complicated port and packages. >> > > Well this is what the makefile will usually do for you... (the Makefile > can be considered a script or you can just get it to run your script). > > Read the porters handbook - it's all there unless you are trying to get it > to help you create the installation script that is in the tarball - which > is not - it will tell you how to work with FreeBSD once you have a working > installation. >> Porters Handbook is here: >> http://www.freebsd.org/doc/en/books/porters-handbook/ >> > > Regards, > > Michelle > > -- > Michelle Sullivan > http://www.mhix.org/ > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >