Opened 15 months ago
Last modified 15 months ago
#68049 assigned defect
mbedtls, mbedtls3: could we make these non-conflicting?
Reported by: | barracuda156 | Owned by: | Schamschula (Marius Schamschula) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Cc: | mascguy (Christopher Nielsen) | |
Port: | mbedtls, mbedtls3 |
Description
Both have ports depending on them, but currently these two conflict.
Change History (4)
comment:1 Changed 15 months ago by mascguy (Christopher Nielsen)
Cc: | mascguy added |
---|
comment:2 follow-up: 3 Changed 15 months ago by Schamschula (Marius Schamschula)
comment:3 Changed 15 months ago by mascguy (Christopher Nielsen)
Replying to Schamschula:
Probably.
However, mbedtls uses
cmake
, so changing the target install path is not as easy as specifyingprefix=/some/path
.Secondly, you have to insure that ports that depend on
mbedtls
can find the correct version or both versions.
Well, this really should he done, to ensure that users can install ports without being blocked by this.
With the caveat that both should be segregated, otherwise it's a major pain to ensure that the wrong one isn't accidentally used.
We've done it for numerous others - the selection of libfmtXX
ports, for example - and it's not that difficult. Just a bit tedious.
comment:4 Changed 15 months ago by mascguy (Christopher Nielsen)
It looks like the total number of dependents across both, is less than 10. So not bad at all.
Sergey, perhaps you'd like to take a stab at this via a PR?
Probably.
However, mbedtls uses
cmake
, so changing the target install path is not as easy as specifyingprefix=/some/path
.Secondly, you have to insure that ports that depend on
mbedtls
can find the correct version or both versions.