Prev: INDEX build failed for 6.x
Next: security/krb5 broken: pkinit_crypto_openssl.c: In function'cms_signeddata_verify'
From: =?UTF-8?Q?Ry=C5=8DTa_SimaMoto?= on 9 Apr 2010 14:16 Hi, I'm new to this list. I'm a member of the GIMP Help Documentation Team. On early October of last year, we released the new version product gimp-help-2.6.0-html, so I edited its port(s). Since this version, we had been providing packages in ready-to-install packages separated in translated languages. Source tarball doesn't exist. On the contrary, Older version was a source tree of XML files. I wrote new ports in two approach for construction: 1. Update only on the graphics/gimp-help. User can select languages by the option function. It is simple, but this way causes its package file to become very bigger than the older version if all languages are included because shared image files are also copied in different paths of each language. about 347MB. 2. Separate the port by languages. In this way, 13 new ports will be added. <graphics/gimp-help> will be changed to the meta-port, <misc/gimp-help-en> as the main port, and other ports as its slaves. Which style is more preferable? Or you have another ways? In the second approach, I don't know how to create 'diff' file for updating these port. The first one is ready to send-pr. -=-=-=-=-= SimaMoto,RyÅTa <liangtai.s4(a)gmail.com> http://code.google.com/p/gimp-doc-ja/ _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |