From owner-freebsd-ports@FreeBSD.ORG Thu Jan 12 18:19:42 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C7B0106564A for ; Thu, 12 Jan 2012 18:19:42 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0C3FB8FC13 for ; Thu, 12 Jan 2012 18:19:41 +0000 (UTC) Received: by obbta17 with SMTP id ta17so1637473obb.13 for ; Thu, 12 Jan 2012 10:19:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=D04XVLdxf9p12hKvET1vgkU9ZpPGCGWAtgkzPK9klqw=; b=XdpTlDHxTokByVAF7JeusvqbMCr8/sQjvhJsQ1aG3UHXEGREuYzaYzHgV0RH1V9ir8 zBuuqcdi/UCRlBTGYRQPRdBREY8j42ekzPH2wCnTHMR2shxDe3EbIK4BKfSi3s/2dSrl 1a6LhJB2xSjYYsrOC5oP+xKaHYKs9sqgB8ejM= Received: by 10.50.193.229 with SMTP id hr5mr5306743igc.15.1326392381317; Thu, 12 Jan 2012 10:19:41 -0800 (PST) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.207.7 with HTTP; Thu, 12 Jan 2012 10:19:08 -0800 (PST) In-Reply-To: <4F0ED159.2060307@herveybayaustralia.com.au> References: <4F0446B7.4090703@herveybayaustralia.com.au> <20120104142757.1c77c347@ernst.jennejohn.org> <4F04E648.9090206@herveybayaustralia.com.au> <20120105121825.656677e4@ernst.jennejohn.org> <20120106221610.00005fbe@unknown> <20120108160316.00003d59@unknown> <4F0A8164.9090502@herveybayaustralia.com.au> <20120110221115.00007dc1@unknown> <4F0CDB5B.9030402@herveybayaustralia.com.au> <4F0DB794.7000600@infracaninophile.co.uk> <4F0E8145.30203@herveybayaustralia.com.au> <4F0E91A0.7000909@infracaninophile.co.uk> <4F0ED159.2060307@herveybayaustralia.com.au> From: Chris Rees Date: Thu, 12 Jan 2012 18:19:08 +0000 X-Google-Sender-Auth: 6mFPOQVGlrphi6fUdndqevPRnrk Message-ID: To: Da Rock Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-ports@freebsd.org Subject: Re: linux-f10-nss_ldap: my first port - be gentle :) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2012 18:19:42 -0000 On 12 January 2012 12:26, Da Rock wrote: > On 01/12/12 17:54, Matthew Seaman wrote: >> >> On 12/01/2012 06:44, Da Rock wrote: >>> >>> I have a Makefile, pkg-desc, pkg-plist, pkg-message, distinfo. I also >>> have the files hosted and the MASTER_FILES set to include the linux >>> sites (just where the files are located). I am looking for a backup sit= e >>> to all that IF I can twist someones arm? >>> >>> I have triple tested it all in all iterations and its as smooth as now- >>> no issues whatsoever. So what happens now? How does it get into the >>> ports tree now? Can someone have a look see and test it before I submit >>> this thing? >> >> Run 'portlint -C' and fix anything it flags up -- well, within reason. >> Sometimes portlint complains about things it shouldn't. >> >> Then submit your port. =A0For a new port, you need to create a .shar of >> the port directory, which you can attach to the PR like so: >> >> =A0 =A0 send-pr -a newport.shar >> >> When filling in the PR in the editor it pops you into, you need to set >> the appropriate field in the PR to 'change-request'. =A0No need to fill = in >> all the sections -- for ports PRs it's mostly 'Description' that gets >> filled in. =A0Everything else is pretty obvious I think. >> >> The comitter who works on the port will run it through tinderbox testing >> and get back to you if there are any problems. > > I would have preferred to know about the -C option earlier- I hadn't > realised how helpful it was. I used -Cv in the end which gave me a better > overview. > > I do have a "WARN: no CVS directories. Use -N to check a new port." Is th= is > normal? Is this simply expected of a new uncommitted port? I assume this = is > the case due to -N mentioned in the warning, I also ran it with -CvN and = it > came back with "looks fine". > > I'll upload a new .shar to my URI now. Hm, for a new port, you should use portlint -A; portlint -C is for existing ports. portlint -A searches for stupid things like a work/ directory still existing too. Chris