RFE: create portlint

[Eric.C.Seidel@…]

A command line tool to verify port integrity would be useful.

Here is a discussion below from IRC:

[22:53] <jkh> portlint.  need it.  must have it.
[22:53] <MacDome> portlint?
[22:53] <jkh> we gotta get the "minimums" codified somehow
[22:53] <MacDome> to check syntax?
[22:54] <jkh> and merely documenting them, though that's a great place to start, is only part of the solution
[22:54] <MacDome> I have already begun discussions with k and l regarding testin... I'll bring that up tomorrow
[22:54] <jkh> syntax and style, yeah
[22:54] <jkh> check for some minimum set of datum and also help validate a $destroot in later incarnations
[22:54] <MacDome> ok
[22:54] <jkh> but some stuff will obviously have to be documentation
[22:55] <jkh> where "elements of style" covers a wider area concerning what makes a good "Mac OS X port" and desired taxonomies
[22:55] <MacDome> ok
[22:55] <jkh> maybe a chapter on when and where to use variants
[22:55] <jkh> encoding OS-dependencies...
[22:55] <jkh> that kinda stuff.  Definitely a living document. :)

[jmpp@…]

Milestone Needs developer review deleted

[afb@…]

Is "port lint" (r28170,r28171) enough to close this ?

[yves@…]

This is great, but is it necessary to have to sudo ? Couldit work like info, list etc ?

[jmpp@…]

I really doubt original proponents of the feature will chime in at any point in these days, so I guess it's up to you, Anders, to determine if your lint code is complete enough to cover for what's discussed here. Based on that you should feel free to close it at any time.

-jmpp

[nox@…]

Added to trunk/ some time ago. let's close this ticket.

[ryandesign@…]

Replying to yves@macports.org:

This is great, but is it necessary to have to sudo ? Couldit work like info, list etc ?

port lint no longer requires root access. See #13458.