libfoo2 vs. libfoo



hello,

so there's no good reason to name the various tarballs "libfoo2".  gtk+
has a special po/Makefile.in.in which uses GETTEXT_PACKAGE to get around
the translations conflicts.

this affects libgnome*, gnome-vfs, gconf, libbonobo*, etc.

are there any problems with going this route?  i plan on doing this in
my snapshot builds, as i'd like the packages to have the same name as
havoc's gnomehide ones, and also not have .mo conflicts.  (ie, i'd be
doing the work and posting patches here and to maintainers).

jacob
-- 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]