Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unversion the .pc ?? #57

Closed
rurban opened this issue Mar 29, 2018 · 1 comment
Closed

unversion the .pc ?? #57

rurban opened this issue Mar 29, 2018 · 1 comment

Comments

@rurban
Copy link
Owner

rurban commented Mar 29, 2018

remove the -3.4 from the .pc, to ease the integration into autotool projects. searching for safec. not safec-3.4, safec-3.3, safec-3.2 ...

See PR #56
versioning was added in the 2nd earliest commit after the sf fork, in 2012.
proper versioning helps in tighten the API to a specific version. "you only get what you asked for."
problem is that only the pkg-config .pc is versioned, (the lib anyway), but not the headers.
thus installing them in parallel will need to override the incdir and the -I path.

when adding the unversioned variant, name if libsafec.pc.

So there are four options:

  1. keep the versioned safe-*.pc asis.
  2. maintain two .pc's, a versioned and an unversioned. I'm leaning towards this one
  3. remove the versioned .pc (as done in PR pkg-config: Rework pkg-config support to be usable #56).
  4. add versioned headers also, into a seperate safec-x.y path.
@rurban rurban changed the title unversion the .pc unversion the .pc ?? May 24, 2019
@rurban
Copy link
Owner Author

rurban commented May 25, 2019

Went with 3. for 3.5

@rurban rurban closed this as completed May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant