Date: Fri, 24 Feb 2012 20:35:18 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Michael Gmelin <freebsd@grem.de> Cc: ports@freebsd.org, Eitan Adler <lists@eitanadler.com> Subject: Re: Newbie maintainer, question regarding patches Message-ID: <4F486506.6050703@FreeBSD.org> In-Reply-To: <EBFDDF5D-6BE4-4BCF-BD0A-C297D3E6DCA2@grem.de> References: <845ACEFD-830F-4941-9EE3-F3CB35FD6200@grem.de> <CAF6rxgmj7V85qrDBoK4ZbmShDLTW-yazUodEgq8KYA3jYYGhxQ@mail.gmail.com> <EBFDDF5D-6BE4-4BCF-BD0A-C297D3E6DCA2@grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/24/2012 06:18, Michael Gmelin wrote: > In general I agree with your reasoning. The feature I'm talking about has been approved and will be in the next version (this happened almost half a year ago). Unfortunately Ice has a slow release cycle, as it is dual licensed (GPLv2+commercial). The next release of Ice is quite a while away and will probably a major release, as they only create releases that are also commercially supported. The vendor doesn't provide any source repository access or anything else that could be used to track new features or patches, they only get announced in the forums. So as a heavy user of this software package I would like to have access to these vendor approved and backwards compatible optional features without working outside of the ports tree. To a certain degree this is comparable to other ports that pull in optional features through patches (djbdns, qmail, nginx, php, etc.). For whatever it's worth, this sounds reasonable to me, and I've done similar in the past with some of my ports. Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F486506.6050703>