Skip to content

Intent of removing .so versions from c4core/c4log/c4fs? #8

@musicinmybrain

Description

@musicinmybrain

I’ve packaged c4core, c4log, and c4fs on Fedora Linux in preparation for packaging rapidyaml (almost done!)

The change in 436b163 means that these libraries no longer have an SONAME, so I would have to either:

  1. start versioning the libraries downstream (basically, carry a patch reverting this commit forever)—which is feasible—or
  2. give up on packaging these libraries separately from rapidyaml—which I am permitted to do, subject to conditions, if I absolutely have to, but which has disadvantages from a distribution packager’s point of view.

Is this the intended effect of this commit? Does it solve a problem in a different environment? Can it be conditionalized such that I can turn versioning back on when packaging system copies of these libraries?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions