Re: openoffice2-bin language packs

On Thu, Mar 15, 2007 at 01:00:43AM +0100, Francis GUDIN wrote:
> 1- is renaming those packages OK ? This would look more consistent to my
> eyes:
> 
> -PKGNAME=		openoffice-bin-${LANGUAGE}-${OO_RELEASE}
> +PKGNAME=		openoffice2-bin-${LANGUAGE}-${OO_RELEASE}
> 
> ( -> openoffice2-bin-langs/Makefile.common)

Strangely, misc/openoffice2 is called openoffice2, but
misc/openoffice2-bin is called openoffice-bin. We should probably
rename that then too.

Renaming them is fine, but you need to add CONFLICTS lines, because
openoffice2-bin-LANG should not be installed at the same time as
openoffice-bin-LANG, because they overwrite each other's lines.
Just add
CONFLICTS+=		openoffice-bin-${LANGUAGE}-[0-9]*

> 2- misc/openoffice2-bin's PKGNAME changed on Feb 27th (PKGREVISION=1).
> Is there a better way to handle that ?:
> 
> -DEPENDS+= openoffice-bin-${OO_RELEASE}:../../misc/openoffice2-bin
> +DEPENDS+= openoffice-bin-${OO_RELEASE}nb1:../../misc/openoffice2-bin

Something like
+DEPENDS+= openoffice-bin-${OO_RELEASE}{,nb*}:../../misc/openoffice2-bin

> 3- RPMs available at ftp://ftp.openoffice.cz/ "fluctuate":
>   - a few new packs appeared: en-US, ka, ku, tg and vi
>   - several packs are no longer available for OOo 2.1: af, bn, br, nr,
>     st, tn, ts, xh and zu
> I could create the missing pkgs, but how to deal with the second list ?
> Should we leave them alone for now, or delete them ?

Yes, remove them. There's not much point if they are not maintained
upstream.

Cheers,
 Thomas

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV