From owner-freebsd-ports Sun Sep 24 10:40:48 2000 Delivered-To: freebsd-ports@freebsd.org Received: from mailout1.hananet.net (mailout1.hananet.net [210.220.163.34]) by hub.freebsd.org (Postfix) with ESMTP id 0F67637B42C for ; Sun, 24 Sep 2000 10:40:44 -0700 (PDT) Received: from gnomaniac.myhome ([211.58.2.139]) by mailout1.hananet.net (Netscape Messaging Server 4.15) with ESMTP id G1EJRU00.212; Mon, 25 Sep 2000 02:40:42 +0900 Received: (from cjh@localhost) by gnomaniac.myhome (8.11.0/8.11.0) id e8OHddf01539; Mon, 25 Sep 2000 02:39:39 +0900 (KST) (envelope-from cjh@kr.FreeBSD.org) X-Authentication-Warning: gnomaniac.myhome: cjh set sender to cjh@kr.FreeBSD.org using -f To: "Michael C . Wu" Cc: freebsd-ports@FreeBSD.org Subject: Re: ports/21504: New port: korean/tin References: <200009240200.TAA12890@freefall.freebsd.org> <20000924040550.A8771@peorth.iteration.net> From: CHOI Junho Date: 25 Sep 2000 02:39:39 +0900 In-Reply-To: "Michael C . Wu"'s message of "Sun, 24 Sep 2000 04:05:51 -0500" Message-ID: <86d7htofj8.fsf@gnomaniac.myhome> Lines: 77 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "MCW" == Michael C Wu writes: > I think chinese/tin or korean/tin you suggested is too simple for > making separated ports. Just install news/tin and edit configuration > file is fine for us. MCW> What about the people who do not know English well enough to MCW> spend all the time doing documentation? True, most FreeBSD MCW> users are able to read English, but it may take quite an effort MCW> to do so. :) MCW> Following your reasoning, there really is no need for any language MCW> ports. After all, they are all just small patches and configurations MCW> for the users. But, is that not what the Ports collection is? :-) I am a maintainer of many language ports in korean category. I think, some useful patches cannot be included in the master source will be good, but changing just configuration is not acceptable. Then, we can have separate ko-windowmaker, ja-windowmaker, zh-windowmaker, etc... for just changing default fontset. Same thing also applies many *-i18n ports. Do you want to do so? :) My guideline is as follows: - accept meaningful patches. It can't achieved without ports, because patches should be applied in the _build_ stage. - don't accept configuration patches just changing default configuration. we can get desired results _after_ installing binary packages(or use ports) and editing my configuration files. That's the difference I want to say. > Or, please make slave ports just like chinese/mutt. MCW> I agree that slave ports are better, but sometimes patches MCW> just do not work with newer versions when the master port MCW> gets updated with newer versions. MCW> Sometimes, when newer versions of software convert to newer MCW> standards like XIM or UTF-8, they break the patches completely. Yes. I agree. It's my preference. But I think we would be not too late to make non-slave language ports after the master changed dramatically. > To other ports developers: Can we accept localized ports doing just > "changing default configuration to local language"? MCW> The Ports collection has accepted that in the past. Also, MCW> following your reasoning, we should not have apache-* ports, MCW> nor xemacs-*/mule-* ports, because they are just configurations MCW> varying by user. :) Oh, these ports is different in this case because we can't get each separated port features without _recompiling_. Can you have apache-ipv6 after installing apache ports and editing just httpd.conf? :) MCW> To summarize, here are some reasons to have non-slave language ports: MCW> o Saves users time from reading English documentation MCW> o The Ports are small patches and configurations, and a language port MCW> follows the same reasoning. MCW> o Newer versions of master ports may prevent the older language patches MCW> of language ports from working. Sometimes developers are not MCW> able to patch the software without large significant structural changes MCW> to the software. Yes. But I need more strict guidelines. -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho KFUG Web Data Bank FreeBSD, GNU/Linux Developer http://people.FreeBSD.org/~cjh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message