Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Dec 2016 09:53:31 +0100
From:      Emanuel Haupt <ehaupt@FreeBSD.org>
To:        Alan Braslau <alan.braslau@comcast.net>
Cc:        ports@freebsd.org
Subject:   making ICONV default net/rsync option (was: Re: rsync port)
Message-ID:  <20161207095331.880d80ef4dfe640e2f50dcbb@FreeBSD.org>
In-Reply-To: <20161206113017.6777549d@zoo.hsd1.co.comcast.net>
References:  <20161206113017.6777549d@zoo.hsd1.co.comcast.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Alan Braslau <alan.braslau@comcast.net> wrote:
> Hello,
> 
> The iconv option of the rsync port is extremely useful, indeed
> necessary when exchanging files with systems that have different
> encoding (such as MacOS).
> 
> It might be useful to create a dependent port, net/rsync-iconv, that
> would include this option by default. This way, one could use binary
> packages without compiling from /usr/ports.
> 
> Currently, I install in jails a binary package in that I created
> locally. However, updating always proposes to replace this package
> with the standard one due to changed options. I do not know of a way
> to avoid this other than through the creation of the dependent port
> as suggested here. If this not be a good idea, might you have any
> other suggestions?
> 
> Thank you, in advance.
> 
> -- 
> Alan Braslau
> 

I agree that the ICONV options is indeed very useful. I wouldn't mind
turning it on by default rather than creating an extra slave port.
After all it is a standard configure option and not a third party patch.

I'm cc'ing ports@ for discussion.

Emanuel



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161207095331.880d80ef4dfe640e2f50dcbb>