ObjFW  History Of Ticket 31bfd1cf2d9874a9c76eaa75b8290f20524222d4

Artifacts Associated With Ticket 31bfd1cf2d9874a9c76eaa75b8290f20524222d4

1. Ticket change [fa3e4728f6] (rid 40873) by js on 2022-11-27 17:47:47:

   1. icomment:

      When disabling some features via `./configure --disable-*`, the resulting shared library has the same name as if all features were enabled. This is problematic, as it essentially creates incompatible versions. Instead, the shared library should be renamed so that only the full version is called libobjfw.
      
      Alternative, only allow disabling features when only building a static library, as there is very little reason to disable features in the shared library.
      

   2. login: "js"
   3. milestone initialized to: "1.0"
   4. mimetype: "text/x-markdown"
   5. priority initialized to: "High"
   6. severity initialized to: "Severe"
   7. status initialized to: "Open"
   8. title initialized to: "Rename the library when features are disabled"
   9. type initialized to: "Enhancement"

2. Ticket change [eb1178cbd3] (rid 41832) by js on 2023-01-14 16:55:18:

   1. icomment:

      Actually, ultimately, this is up to distributions. It also means its up to them if they break ABI by disabling feature from one release to the next.
      
      On systems that don't have a single source for packages, software that ships ObjFW should either statically link or install a version of ObjFW with all features enabled, but that's hard or even impossible to enforce.
      

   2. login: "js"
   3. mimetype: "text/x-markdown"
   4. resolution changed to: "Rejected"
   5. status changed to: "Closed"