Opened 14 months ago
Last modified 14 months ago
#72473 new defect
p5-pod-markdown has nonsensical binary installed
| Reported by: | FGasper (Felipe Gasper) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | p5-pod-markdown |
Description (last modified by FGasper (Felipe Gasper))
The p5-pod-markdown port is replaced by p5.34-pod-markdown. That port, though, installs a binary named /opt/local/bin/pod2markdown-5.34.
This isn’t very helpful for scripts that expect to find a pod2markdown binary (without the version suffix). If I port install p5-pod-markdown, it seems logical that a pod2markdown command/binary/symlink be made available as a result.
Should p5-pod-markdown instead maybe be defined as a thin wrapper around the p5.34 port, that just installs a symlink to it?
Thank you!
Change History (2)
comment:1 Changed 14 months ago by FGasper (Felipe Gasper)
| Description: | modified (diff) |
|---|
comment:2 Changed 14 months ago by ryandesign (Ryan Carsten Schmidt)
| Port: | p5-pod-markdown added |
|---|
Note: See
TracTickets for help on using
tickets.
Your observations could apply to any of the thousands of p5- ports, and no, no such changes are intended. You might, after all, wish to use a different version of perl. How should p5-pod-markdown or any of the other p5- ports know which one?