Date: Thu, 12 Jan 2012 18:19:08 +0000 From: Chris Rees <crees@freebsd.org> To: Da Rock <freebsd-ports@herveybayaustralia.com.au> Cc: freebsd-ports@freebsd.org Subject: Re: linux-f10-nss_ldap: my first port - be gentle :) Message-ID: <CADLo83_J0=jjK0cgk6XNR1wNoLVCSHBWJ0iFzsjEH6oxBKQwMA@mail.gmail.com> 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> <CADLo83-YUtUgAw_r2QNpB2mPxbvPfV0vCRMih-ncAQBCWj73LQ@mail.gmail.com> <20120108160316.00003d59@unknown> <4F0A8164.9090502@herveybayaustralia.com.au> <20120110221115.00007dc1@unknown> <4F0CDB5B.9030402@herveybayaustralia.com.au> <EBA4CEA9D06CDF6C3E6F5095@utd71538.utdallas.edu> <CAF6rxgmYfKm=qYJXJfAJniyuxA1jm6zX=m9KP9YBqCmmse8ykQ@mail.gmail.com> <4F0DB794.7000600@infracaninophile.co.uk> <4F0E8145.30203@herveybayaustralia.com.au> <4F0E91A0.7000909@infracaninophile.co.uk> <4F0ED159.2060307@herveybayaustralia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 January 2012 12:26, Da Rock <freebsd-ports@herveybayaustralia.com.au> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83_J0=jjK0cgk6XNR1wNoLVCSHBWJ0iFzsjEH6oxBKQwMA>