#677: Which tools/*/*.pl programs belong in which tools/* directory?
-----------------------+----------------------------------------------------
 Reporter:  jkeenan    |       Owner:  jkeenan 
     Type:  cage       |      Status:  assigned
 Priority:  minor      |   Milestone:          
Component:  configure  |     Version:  1.1.0   
 Severity:  low        |    Keywords:  tools   
     Lang:             |       Patch:          
 Platform:             |  
-----------------------+----------------------------------------------------
Changes (by jkeenan):

  * owner:  => jkeenan
  * status:  new => assigned


Comment:

 Replying to [comment:5 wayland]:
 > Here's some suggested documentation until we have something better:
 >
 > -----
 >
 > The tools/ directory was begun as an ad-hoc collection of random files.
 This guideline suggests what kind of files go where.  It is hoped that,
 over time, the files will migrate to the places suggested in this
 guideline.  If you really want to put a file somewhere where this
 guideline doesn't suggest, then that probably means that this guideline
 needs updating.
 >
 > build   Tools called by the build process
 >
 > dev     Tools that are called on a one-off, ad-hoc basis by developers
 >
 > docs    Tools that help generate the documentation from source
 >
 > install Not sure about these; they're probably good for something
 >
 > util    No rule appears to govern these either; maybe they should be
 merged with "dev"
 >

 Wayland,

 I was thinking about this overnight and came to very similar conclusions.
 I think ''tools/build'' should hold programs invoked by ''make'' (or, more
 precisely, ''make all'').  ''tools/install/'' should hold the two install
 programs.  ''tools/docs'':  self-explanatory.  ''tools/dev'':  probably
 everything else, including ''make'' targets other than ''all'',
 ''install'' and ''install-dev''.

 We'll need to make up a list of programs which need to be migrated from
 one directory to another.  We should also try to determine a Parrot Design
 Document location in which to place whatever rule we decide upon.

 Thank you very much.

 kid51

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/677#comment:6>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to