Date: Tue, 29 Apr 2014 08:15:42 +0400 From: Boris Samorodov <bsam@passap.ru> To: pauline martin <321eniluap@gmail.com>, freebsd-ports@freebsd.org Subject: Re: New port or update an old one? Message-ID: <535F276E.80507@passap.ru> In-Reply-To: <CAPVj7Ye9bffLwkz2NBXgn-f5A==Cw0xxDELp36i9GYt-VrZ_yA@mail.gmail.com> References: <CAPVj7Ye9bffLwkz2NBXgn-f5A==Cw0xxDELp36i9GYt-VrZ_yA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?535F276E.80507>