Make a note about how we don't handle release-less properties.
authorKristian H?gsberg <krh@redhat.com>
Sun Apr 06 18:40:53 2008 -0400 (2008-04-06)
changeset 1894b7eca63fb6d
parent 188 a272b6ce454b
child 190 d8b7dd11813d
Make a note about how we don't handle release-less properties.

Such as requires: glibc > 2.6.90.
TODO
     1.1 --- a/TODO	Sun Apr 06 00:29:47 2008 -0400
     1.2 +++ b/TODO	Sun Apr 06 18:40:53 2008 -0400
     1.3 @@ -11,6 +11,21 @@
     1.4  
     1.5     - store rpm headers for installed packages.
     1.6  
     1.7 +- rpm seems to consider glibc > 2.6.90 to mean greater than
     1.8 +  2.6.90-anything.  That is, a comparison that doesn't mention the
     1.9 +  release field, shouldn't regard the release field of pkgs it
    1.10 +  compares against.  glibc-common-2.6.90 has
    1.11 +
    1.12 +	conflicts: glibc < 2.6.90, glibc > 2.6.90
    1.13 +
    1.14 +  since rpm doesn't let you do glibc != 2.6.90, and
    1.15 +
    1.16 +	requires: glibc = 2.6.90
    1.17 +
    1.18 +  will always pull in glibc.  But even with a != relation, would
    1.19 +  glibc-2.6.90-16 be equal to 2.6.90?  glibc 2.7.90-8 dropped it in
    1.20 +  favor of requires = 2.7.90-8 (#225806).
    1.21 +
    1.22  - signed packages
    1.23  
    1.24  - download (libcurl?)