From owner-freebsd-ports@FreeBSD.ORG Thu Jun 30 12:08:24 2011 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 1EB43106566B for ; Thu, 30 Jun 2011 12:08:24 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id F0F898FC0A for ; Thu, 30 Jun 2011 12:08:23 +0000 (UTC) Received: by pvg11 with SMTP id 11so2250906pvg.13 for ; Thu, 30 Jun 2011 05:08:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=q3g/cmsJGjurXlhdeO5fFI2gamH0kD3sE0ns1vSh+aw=; b=vi+r+qhPP2Iy7H8dtcQSGHdhHpI81US5cq9fTP1c8vM1qWkMRQ4njWHA2AE5qX+ymw hBNikcOpxl3+Z7zbCtQGgnw6YJH4sVkJ+RmjTNtVMfQaEgn+GoW727tQMhzi3nZNyHug 4/PH9kTWt9/hdPStzBjUwDAtZ+l02sqWSw7FM= MIME-Version: 1.0 Received: by 10.68.40.161 with SMTP id y1mr2449762pbk.156.1309435703359; Thu, 30 Jun 2011 05:08:23 -0700 (PDT) Received: by 10.68.64.104 with HTTP; Thu, 30 Jun 2011 05:08:23 -0700 (PDT) Date: Thu, 30 Jun 2011 12:08:23 +0000 Message-ID: From: "b. f." To: freebsd-ports@FreeBSD.org, mandree@FreeBSD.org, secn3t@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: [Adopting a port..or contributing... and a patch included for java on most recent of all jdk/jre) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2011 12:08:24 -0000 > Am 30.06.2011 04:23, schrieb xD 0x41: > *For your next submission*, please keep the information below in mind so > we can actually use your contribution: > > In a common work flow, you'd usually first update the ports tree (for > instance, running "portsnap fetch update", or for the first time, > "portsnap fetch extract"), Some alternative updating methods (anonymous cvs, cvsup/csup, rsync, ctm, ftp) are in: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html >do "make checksums" on the old port before a typo, the target is "checksum", no trailing s (for reference, the targets are documented in the Makefiles in ports/Mk, and in the PORTS(7) manpage) > touching the Makefile so that the other and/or old files are there and > properly downloaded (except if all distfiles change, even if "all" means > just one) > > To generate the sha256 for the files, all it takes is to download the > new files, verify it's properly downloaded and untampered (best with > GnuPG signatures if available), put it in /usr/ports/distfiles (or a > subdirectory, if specified in the Makefile), and then "make makesums" a typo, the target is "makesum", no trailing s > will do the job. That also works outside the ports directory tree, if > you copy the original port and work on the copy. > > Finally, to ease tracking of your contribution, and make sure it isn't > lost, it's useful if you > > A. either use the port-tools to submit the patches with the "port > submit" command as a "PR", Note that "port" is a utility from the ports-mgmt/porttools port, which must be installed -- it is not in the base system or in ports/Tools. If you are going to use this, consider running "port test" on your patched port before proposing changes. b.