Date: Sat, 31 Aug 2002 09:12:41 -0300 From: Mario Sergio Fujikawa Ferreira <lioux@FreeBSD.org> To: Oliver Braun <obraun@informatik.unibw-muenchen.de>, ports@freebsd.org, B.Candler@pobox.com, dwcjr@freebsd.org, jos@catnook.com Subject: Re: Please review patch (was: ports/42074: rsync depends on many other packages - popt dependencies?) Message-ID: <20020831121303.86543.qmail@exxodus.fedaykin.here> In-Reply-To: <20020829085624.GA63657@informatik.unibw-muenchen.de> References: <200208271204.g7RC4jBG049111@www.freebsd.org> <20020829085624.GA63657@informatik.unibw-muenchen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Sorry for the awful delay on picking up this thread. :( I was otherwise engaged with other problems.... On Thu, Aug 29, 2002 at 10:56:02AM +0200, Oliver Braun wrote: > * Brian Candler <B.Candler@pobox.com> [2002-08-27 14:04 +0200]: > > Possibly as a result of change ports/37348, rsync now depends on a > > whole bunch of other packages including an XML parser! >=20 > > This is a bit of a pain in a server environment where you want to > > install the minimum amount of shrapnel. libpopt I will accept, but > > the rest seem irrelevant to rsync. >=20 > > expat/libiconv/gettext are dependencies of popt, so I guess the > > question really is why a command-line option parser depends on those > > things? So that it can resolve any locale things. As I understand popt uses gettext so that it can return localized error messages. And to be able to handle localized parameters, e.g., diacriticals (=E1, that is a á in case your terminal did not show). Both expat and libiconv are side effects of having gettext as a dependency. :( > Find attached a patch I want to commit: >=20 > * define WITH_POPT_PORT to build net/rsync with devel/popt and all > dependencies. > * default behaviour is to use included popt. So, the package does not > depend on devel/popt >=20 > Lioux, does devel/popt need all these dependencies, or is it possible to > remove the dependency on gettext at least by default and make gettext > support optional? At the current stage of things, there are 2 side effects of making gettext support optional (if that is at all possible, I haven't investigated yet): 1) It will drop down localized support which may not be important for the messages but IS for the parameters 2) It will break the dependency list for several ports. Some of them relied on the fact that gettext already pulled either libiconv or expat as dependencies. So we would have to identify and explicitily add dependencies to some ports Having said this, I do not feel strongly about keeping gettext personally. However, we should consider the possible impact on the functionality of our ports. As well as the fixes necessary to make sure the ports will keep on working after this. Regards, -- Mario S F Ferreira - DF - Brazil - "I guess this is a signature." Computer Science Undergraduate | FreeBSD Committer | CS Developer flames to beloved devnull@someotherworldbeloworabove.org feature, n: a documented bug | bug, n: an undocumented feature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020831121303.86543.qmail>