Changes between Initial Version and Version 6 of Ticket #463


Ignore:
Timestamp:
Aug 28, 2007, 3:18:52 AM (17 years ago)
Author:
jmpp@…
Comment:

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

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #463

    • Property Cc afb@… jkh@… nox@… added
    • Property Summary changed from portlint to RFE: create portlint
    • Property Priority changed from Expected to Normal
    • Property Version changed from 1.0 to
    • Property Milestone changed from to MacPorts base enhancements

  • Ticket #463 – Description

    initial v6  
    33Here is a discussion below from IRC:
    44
    5 [22:53]         <jkh>   portlint.  need it.  must have it.
    6 [22:53]         <MacDome>       portlint?
    7 [22:53]         <jkh>   we gotta get the "minimums" codified somehow
    8 [22:53]         <MacDome>       to check syntax?
    9 [22:54]         <jkh>   and merely documenting them, though that's a great place to start, is only
    10 part of the solution
    11 [22:54]         <MacDome>       I have already begun discussions with k and l regarding testin... I'll bring
    12 that up tomorrow
    13 [22:54]         <jkh>   syntax and style, yeah
    14 [22:54]         <jkh>   check for some minimum set of datum and also help validate a $destroot in
    15 later incarnations
    16 [22:54]         <MacDome>       ok
    17 [22:54]         <jkh>   but some stuff will obviously have to be documentation
    18 [22:55]         <jkh>   where "elements of style" covers a wider area concerning what makes a good
    19 "Mac OS X port" and desired taxonomies
    20 [22:55]         <MacDome>       ok
    21 [22:55]         <jkh>   maybe a chapter on when and where to use variants
    22 [22:55]         <jkh>   encoding OS-dependencies...
    23 [22:55]         <jkh>   that kinda stuff.  Definitely a living document. :)
     5{{{
     6[22:53] <jkh> portlint.  need it.  must have it.
     7[22:53] <MacDome> portlint?
     8[22:53] <jkh> we gotta get the "minimums" codified somehow
     9[22:53] <MacDome> to check syntax?
     10[22:54] <jkh> and merely documenting them, though that's a great place to start, is only part of the solution
     11[22:54] <MacDome> I have already begun discussions with k and l regarding testin... I'll bring that up tomorrow
     12[22:54] <jkh> syntax and style, yeah
     13[22:54] <jkh> check for some minimum set of datum and also help validate a $destroot in later incarnations
     14[22:54] <MacDome> ok
     15[22:54] <jkh> but some stuff will obviously have to be documentation
     16[22:55] <jkh> where "elements of style" covers a wider area concerning what makes a good "Mac OS X port" and desired taxonomies
     17[22:55] <MacDome> ok
     18[22:55] <jkh> maybe a chapter on when and where to use variants
     19[22:55] <jkh> encoding OS-dependencies...
     20[22:55] <jkh> that kinda stuff.  Definitely a living document. :)
     21}}}