#57855 closed defect (wontfix)
py27-cairo: Add ucs4 variant
| Reported by: | sharris40 (Spencer Harris) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | py27-cairo |
Description
If python27 is built with +ucs4, py27-cairo must be rebuilt from source. To ensure we don't download the binary packages by mistake, we can add a ucs4 variant to py27-cairo and require it to be active if python27 has the ucs4 variant active.
This issue might apply to other py27-* ports as well.
Change History (2)
comment:1 Changed 6 years ago by jmroot (Joshua Root)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 Changed 6 years ago by jmroot (Joshua Root)
Note: See
TracTickets for help on using
tickets.
I'm pretty sure this applies to all extension modules that do anything with strings. Variants aren't a good fit for this problem because having a particular variant selected in the python27 port doesn't force that variant to be selected in its dependents, nor vice versa. Making UCS4-flavoured subports of python27 and all ports that install extension modules would be a lot more trouble than it's worth IMO. I wouldn't go so far as to remove the variant from python27 entirely as some have suggested, but putting a big warning on it makes sense.