SPECS (rpm-4_5): rpm.spec - deem. need different sources for db due md5

[Jeff Johnson]

On Sep 3, 2008, at 2:51 PM, Jakub Bogusz wrote:

>
>
> As for db maintenance - I though about db changes themselves, not
> clashes.
>

There are no changes to internal db in rpm. The possible exception
is "robust mutex" handling, but one can live without that functionality.

> Currently _this_ bug is worked around by internal db used in  
> nss_db, but
> it seems more general problem with glibc importing too much from nss
> module (think about different versions of mysql or ldap libs).
> I'm not sure if it still exists with current glibc, IIRC I've seen  
> some
> comments on libc-alpha or so.
>

Note that nss has its own bloat through internal db. So
    two faults == rpm error
as always.

>
> BTW, just found funny rpm "bug" (originated from patch about 9 years
> ago, when rpm didn't accept specs with non-ascii characters):
> https://bugzilla.redhat.com/show_bug.cgi?id=226377#c14
>

;-) Yes hysterical.

What is less hysterical is this bug:
     http://rpm5.org/cvs/tktview?tn=38,5

No encoding can be specified for tags in a *.spec file. And so  
stoopid checks
like what the comment in bz#226377 is attached to are all that can be  
attempted
9+ years later. Sad but true.

The underlying __DESIGN__ problem in rpm is that RPM_I18NSTRING_TYPE,  
an associative
array using locale, to return a string with no obviious or reliable  
means to handle encoding
transforms.

But I digress ...

73 de Jeff
>
> -- 
> Jakub Bogusz    http://qboosh.pl/
> _______________________________________________
> pld-devel-en mailing list
> pld-devel-en at lists.pld-linux.org
> http://lists.pld-linux.org/mailman/listinfo/pld-devel-en