From owner-freebsd-ports@FreeBSD.ORG Tue Apr 29 04:15:47 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 342606E3 for ; Tue, 29 Apr 2014 04:15:47 +0000 (UTC) Received: from forward7l.mail.yandex.net (forward7l.mail.yandex.net [IPv6:2a02:6b8:0:1819::7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E76CEC5B for ; Tue, 29 Apr 2014 04:15:46 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward7l.mail.yandex.net (Yandex) with ESMTP id 3A05DBC105F; Tue, 29 Apr 2014 08:15:43 +0400 (MSK) Received: from smtp11.mail.yandex.net (localhost [127.0.0.1]) by smtp11.mail.yandex.net (Yandex) with ESMTP id D11B77E00AC; Tue, 29 Apr 2014 08:15:42 +0400 (MSK) Received: from 78.108.203.86.tel.ru (78.108.203.86.tel.ru [78.108.203.86]) by smtp11.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id lkG2LQs5AF-FgWWjWVV; Tue, 29 Apr 2014 08:15:42 +0400 (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) X-Yandex-Uniq: 91aeeda7-0dcc-44f4-a301-d7ff0a277b9f Message-ID: <535F276E.80507@passap.ru> Date: Tue, 29 Apr 2014 08:15:42 +0400 From: Boris Samorodov Organization: =?UTF-8?B?0JfQkNCeICLQktCQ0KDQoiI=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: pauline martin <321eniluap@gmail.com>, freebsd-ports@freebsd.org Subject: Re: New port or update an old one? References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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: Tue, 29 Apr 2014 04:15:47 -0000 28.04.2014 18:59, pauline martin пишет: > > I have recently forked and updated k9copy. It now builds with the current > developmental releases of ffmpeg. I intend to keep making improvements to > the project and I would like to see it get into the ports tree. I have > written and tested a ports Makefile, pkg-plist, etc. However, I do not > know whether the correct procedure in this situation (seeing as it is > technically a fork), would require that I ask and wait for a response from > the current maintainer of k9copy (in the ports tree as k9copy-kde4) or if I > should submit it as a new port. The current one in the ports tree is > release 2.3.4, the last of the original developer's releases was 2.3.8. Sure, it's (2.3.4 -> 2.3.8) an update. Please, send a PR with your patch. Then when (if) the maintainer approves, it will be committed. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve