<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Mar 26, 2016, at 12:15 PM, Ankit Agarwal <<a href="mailto:ankit@ankit.im" class="">ankit@ankit.im</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><span class="im" style="font-size:13px"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="color:rgb(55,61,73);font-family:Georgia,Cambria,serif;font-size:14px" class="">It is a convention to name the </span><code style="font-size:1em;color:rgb(199,37,78);background-color:rgb(249,242,244);border-top-left-radius:4px;border-top-right-radius:4px;border-bottom-right-radius:4px;border-bottom-left-radius:4px;padding:2px 4px;font-family:monospace,monospace" class="">.pc</code><span style="color:rgb(55,61,73);font-family:Georgia,Cambria,serif;font-size:14px" class=""> file after the library link-name, so we can determine which </span><code style="font-size:1em;color:rgb(199,37,78);background-color:rgb(249,242,244);border-top-left-radius:4px;border-top-right-radius:4px;border-bottom-right-radius:4px;border-bottom-left-radius:4px;padding:2px 4px;font-family:monospace,monospace" class="">.pc</code><span style="color:rgb(55,61,73);font-family:Georgia,Cambria,serif;font-size:14px" class=""> file to ask </span><code style="font-size:1em;color:rgb(199,37,78);background-color:rgb(249,242,244);border-top-left-radius:4px;border-top-right-radius:4px;border-bottom-right-radius:4px;border-bottom-left-radius:4px;padding:2px 4px;font-family:monospace,monospace" class="">pkg-config</code><span style="color:rgb(55,61,73);font-family:Georgia,Cambria,serif;font-size:14px" class=""> for by parsing the </span><code style="font-size:1em;color:rgb(199,37,78);background-color:rgb(249,242,244);border-top-left-radius:4px;border-top-right-radius:4px;border-bottom-right-radius:4px;border-bottom-left-radius:4px;padding:2px 4px;font-family:monospace,monospace" class="">.modulemap</code><span style="color:rgb(55,61,73);font-family:Georgia,Cambria,serif;font-size:14px" class=""> file in the Swift package.</span></blockquote><div class=""><br class=""></div></span><div style="font-size:13px" class="">what about the cases where .pc file doesn't matches the link-name from modulemap for eg : gtk+2 or 3 has these link-names: `link "gtk-2.0"`, `link "gtk-3.0"` and .pc files are `gtk+-2.0.pc`, `gtk+-3.0.pc`</div><div style="font-size:13px" class=""><br class=""></div><div style="font-size:13px" class="">One option could be an optional in Package -> `pkgconfig: "gtk+-2.0"`</div><div style="font-size:13px" class=""><br class=""></div><div style="font-size:13px" class="">----</div><div style="font-size:13px" class=""><br class=""></div><div style="font-size:13px" class="">Probably not in scope of this proposal, I noticed that pkg-config can give versions of the system libs, would it be a good idea for user to mention a version range of system lib while creating the modulemap wrapper package.</div></div></div></blockquote><br class=""></div><div class="">Our decision here was that if you have CFoo then CFoo2 is the name of the package for the major version bump to 2.</div><div class=""><br class=""></div><div class="">The rationale for this is: this is how it basically works in the C library packaging system currently.</div><div class=""><br class=""></div><div class="">Major version bumps are much rarer and the approach taken by system packagers has been to make entirely new packages for them. Even the .pc files are versioned thus, at least, this is all I’ve ever seen.</div><div class=""><br class=""></div><div class="">It’s not clean, but we’re building on top of what is there.</div></body></html>