#39897: Add 'optional' or 'recommended' metadata tags to portfile spec. --------------------------+-------------------------------- Reporter: c.herbig@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by c.herbig@…): Replying to [comment:4 ryandesign@…]:
Presumably the recommendation would not be printed if the recommended port is already installed. Yeah, that's pretty much what I had in mind.
I would like for each recommendation to be accompanied by an explanation. Users would want to know ''why'' a port is being recommended. For example, if they were told that yelp is used for accessing help content, and the user has no plans to access the help content, then the user will know they don't need to install it. Do you think that simply using the ${description} tag from each recommended port would be satisfactory? It would require that authors use good descriptions. Alternatively, I suppose a description {} keyword could be added to each recommends port line, like variant description {} already does. Or it could be implemented such that if a description {} is not provided, then it defaults to the portfile's description tag.
-- Ticket URL: <https://trac.macports.org/ticket/39897#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X