# New Ticket Created by  James Keenan 
# Please include the string:  [perl #43007]
# in the subject line of all future correspondence about this issue. 
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43007 >


In the 'reconfigure/' branch, I contributed a new file, docs/ 
configure/files.pod, in r18602.  Please find a copy attached.

In April, I wrote on the mailing list:

"So, can someone draw a roadmap of:
"-- *which parts* of Parrot's configuration and build tools *need* to  
be replaced with something else;

"-- *why* that replacement is necessary;

" -- *when* in the design process that replacement must take place; and

" -- *how* that replacement will be maintained going forward from  
there?"

On April 26, Allison Randal responded (http://tinyurl.com/3d48fh):

"The biggest thing we need to start this roadmap is documentation on the
current configuration and build system. The current requirements and
process for building Parrot are the starting point for all future
refinements to the build system. You're in a better position to draft
that than anyone else in the project right now. Interested?"

Whether I actually am in that position is doubtful.  In any event, I  
figured that a good way to start would be to simply list the files  
that are created during configuration, then ask people to write short  
descriptions of their purpose/functions.

Since the files that are created depend on the options with which you  
run Configure.pl, there can be no one, definitive list of those  
files.  So I wrote what is intended to be the first draft of a non- 
authoritative document, one which is supplementary to docs/ 
configuration.pod.

Since the name of this file, what directory it should go in, and what  
it should contain are all up for discussion, I decided not to commit  
this directly to trunk.  However, since we can develop in branches  
where appopriate, I did commit this to the 'reconfigure' branch.  If  
you think this file is worthwhile -- and particularly if you can add  
brief explanations of the purpose of the files created during  
configuration -- please edit in this branch.  Then we'll decided  
whether it should go into trunk and, if so, where.

Thank you very much.
kid51


Attachment: files.pod
Description: Binary data

Reply via email to