Opened 21 years ago
Last modified 15 years ago
#463 closed enhancement
portlint — at Initial Version
Reported by: | Eric.C.Seidel@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | MacPorts 1.6 |
Component: | base | Version: | |
Keywords: | Cc: | ||
Port: |
Description
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. :)