Subject:*
<
Name/Email:*
<
Message Icon:*
<
Select*
<
Message:*
<



Click the Preview to see the content in action.
Options:*
<
Confirmation Code*
<
2 - 0 = ?  
Input the result from the expression
Maximum attempts you can try: 10
*
<
     

Re: Xoops 2.6.0 alpha 3 issues
by Mamba on 2014/1/8 10:30:08

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

With or without Composer, XOOPS should be easy to install, that's a given

But let's see if there is a way to have Composer in the background as part of the Installer, in a way that the user is not even aware of it....
Re: Xoops 2.6.0 alpha 3 issues
by heyula on 2014/1/8 9:43:00

Quote:

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


+1
Re: Xoops 2.6.0 alpha 3 issues
by Bleekk on 2014/1/8 9:34:50

I also think that composer is a nice tool but a cms should be easy to install.
Composer should be a optional feature
Re: Xoops 2.6.0 alpha 3 issues
by tatane on 2014/1/8 9:31:14

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
Re: Xoops 2.6.0 alpha 3 issues
by redheadedrod on 2014/1/8 9:26:59

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.

Who's Online

158 user(s) are online (119 user(s) are browsing Support Forums)


Members: 0


Guests: 158


more...

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits