From: Verdon V. <ve...@ve...> - 2007-01-03 13:54:27
|
Morning :) On 3-Jan-07, at 8:27 AM, Matthew McNaney wrote: > Good morning. > > I am looking for feedback on how the core and modules should be > distributed. > > Initially, modules untarred to their own directory. For example, > blog_1_3_4.tgz would untar as the directory blog/. > > This was confusing some people so I changed it to mod/module_name so > they could be untarred in the root installation. Either of these is fine and intuitive for me, but I think mod/ module_name seems a more common sort of convention. The only problem this might cause is that any 3rd-party mods from the phpws-comm project will not follow this convention and that could lead to confusion for new users. > > As for the core, some people are untarring that distro into the core > directory when, in fact, it needs to be decompressed and copied > into the > root. > > How would you prefer this be done? How would you like the modules and > core to untar? When decompressed, what should the directories be > named? > Is "core" a misleading name for the base files of phpwebsite? I must admit to being slightly confused by this the first time. I too thought that 'core' meant things in the core directory only. It didn't take me long to realize that my assumption was wrong, but I can see the confusion :) Perhaps the word 'core' should be reserved for things in the core dir and some other term used for core files not in the core dir ;-) > > Any advice would be appreciated. Ultimately, it doesn't matter what convention you choose, someone will misunderstand it. The most common convention that I see in other projects is that all updates and patches and add-ons can be expanded into the root dir and the appropriate dir/file structure is reflected in the update/patch/ add-on. salut, verdon |