#46343 closed defect (fixed)
p5-json-pp: make the port obsolete
Reported by: | mojca (Mojca Miklavec) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | p5-json-pp |
Description
The module is part of Perl core since Perl 5.14, there is no longer need to keep the module around, but we probably need to modify it and to declare some replaced_by
.
Change History (3)
comment:1 Changed 10 years ago by dbevans (David B. Evans)
comment:2 Changed 10 years ago by dbevans (David B. Evans)
On second thought, I think you were right in the first place: better to make p5*-json-pp obsolete with no replacement. This is because the port tries to install
${prefix}/bin/json-pp-${perl5.major}
which conflicts with the version in core.
No explicit dependencies on p5-json-pp remain implying that ports that may use it are happy with the version in core.
comment:3 Changed 10 years ago by dbevans (David B. Evans)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Marked obsolete, replaced by perl5.16 (core) in r130545, branches 5.8 5.10 5.12 included. To avoid conflicts p5-json-pp should not be included in p5-graveyard.
Note: See
TracTickets for help on using
tickets.
This is one of a number of ports that are also contained in core in one or more versions of perl. The port, in theory, contains the most recent version of the module while the copy in core may not depending on the perl version involved. Depending on the port version presumably overrides the core version. In this case, it might be used to remedy the case where the core version is too old for some dependent port.
I suggest, since this module is not obsolete (because it is in core in recent versions of perl), that this port should be upgraded by dropping the remaining p5.12 subport and adding p5.16 - p5.20.
See also the discussion concerning the inclusion of this port in p5-graveyard.