On 8/9/06, <b class="gmail_sendername">Khalid B</b> <<a href="mailto:kb@2bits.com">kb@2bits.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 8/9/06, Gary Feldman <<a href="mailto:dpal_gaf_devel@marsdome.com">dpal_gaf_devel@marsdome.com</a>> wrote:<br>> Khalid B wrote:<br>> > Install profile is confusing .<br>> Part of the confusion is that, grammatically, it should be "Installation
<br>> profile." (Nouns can be adjectives, and nouns can be verbed, but verbs<br>> can't be adjectives.)<br>><br>> Installation profile works for me, but I prefer package configuration or<br>> package description. If the file will be *.profile, then package
<br>> profile seems good.<br><br>The main source of confusion, to me, is that it is a term with historical<br>baggage, and its ambiguity means different things to different people.<br><br>Profile can be confused with Drupal's profile module as well.
<br><br>Package seems to convey the right idea, and has no historical<br>use in Drupal.</blockquote><div><br>package == something that can be installed.<br>
<br>
apt == advanced package tool (or similar)<br><br> A theme is a package, and a module is a package and an engine is a package and an install profile/distribution is a package.<br><br>The dependency system (with the .meta files) being developed handles dependencies between all these packages (of different types)
<br><br>I vote for distribution, it is very well suited for our meaning.. and the main reason we want 'install profiles' is because we want to build distributions.<br><br></div></div>