redheadedrod wrote:
Personally I think REQUIRING composer to install xoops is a bad decision. It works (sort of) while under development but it will be a cause for much grief moving forward. A package that a user installs must be seamless and include everything.

I could be wrong but until composer is a default inclusion in PHP I think it is a very bad decision to force people to install composer in order to use xoops. I don't think it is a bad idea to include the code with the installation so someone could update the included packages if they want but 90% of the users that are going to want to install xoops will not want to fuss with having to have to install something else first and it will be a very big and continuous support issue.

tatane wrote:
Quote:

redheadedrod wrote:
Personally I think REQUIRING composer to install xoops is a bad decision. It works (sort of) while under development but it will be a cause for much grief moving forward. A package that a user installs must be seamless and include everything.

I could be wrong but until composer is a default inclusion in PHP I think it is a very bad decision to force people to install composer in order to use xoops. I don't think it is a bad idea to include the code with the installation so someone could update the included packages if they want but 90% of the users that are going to want to install xoops will not want to fuss with having to have to install something else first and it will be a very big and continuous support issue.

+1

I also think that composer is a nice tool but a cms should be easy to install.