Hi all
as I feel that scripts directory has become sort of mess of developer and end user scripts, I would like to move all things which are interesting for end users to examples dir. I've already done this with signon and openid example scripts, the only remaining piece now are SQL scripts for creating phpMyAdmin configuration storage. Any objections against moving SQL scripts there as well?
PS: I'm doing all this in QA_3_5 branch.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le 2012-02-13 07:36, Michal ?iha? a écrit :
Hi all
as I feel that scripts directory has become sort of mess of developer and end user scripts, I would like to move all things which are interesting for end users to examples dir. I've already done this with signon and openid example scripts, the only remaining piece now are SQL scripts for creating phpMyAdmin configuration storage. Any objections against moving SQL scripts there as well?
PS: I'm doing all this in QA_3_5 branch.
Yes, a little objection. I don't find the "examples" directory name very descriptive for these configuration scripts.
- -- Marc Delisle http://infomarc.info
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi
Dne Mon, 13 Feb 2012 08:46:03 -0500 Marc Delisle marc@infomarc.info napsal(a):
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le 2012-02-13 07:36, Michal ?iha? a écrit :
Hi all
as I feel that scripts directory has become sort of mess of developer and end user scripts, I would like to move all things which are interesting for end users to examples dir. I've already done this with signon and openid example scripts, the only remaining piece now are SQL scripts for creating phpMyAdmin configuration storage. Any objections against moving SQL scripts there as well?
PS: I'm doing all this in QA_3_5 branch.
Yes, a little objection. I don't find the "examples" directory name very descriptive for these configuration scripts.
Well neither is "scripts" :-). Anybody has better idea?
- -- Michal Čihař | http://cihar.com | http://blog.cihar.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le 2012-02-13 08:56, Michal Čihař a écrit :
Hi
Dne Mon, 13 Feb 2012 08:46:03 -0500 Marc Delisle marc@infomarc.info napsal(a):
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le 2012-02-13 07:36, Michal ?iha? a écrit :
Hi all
as I feel that scripts directory has become sort of mess of developer and end user scripts, I would like to move all things which are interesting for end users to examples dir. I've already done this with signon and openid example scripts, the only remaining piece now are SQL scripts for creating phpMyAdmin configuration storage. Any objections against moving SQL scripts there as well?
PS: I'm doing all this in QA_3_5 branch.
Yes, a little objection. I don't find the "examples" directory name very descriptive for these configuration scripts.
Well neither is "scripts" :-). Anybody has better idea?
install-scripts ?
- -- Marc Delisle http://infomarc.info
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi
Dne Mon, 13 Feb 2012 09:01:56 -0500 Marc Delisle marc@infomarc.info napsal(a):
Le 2012-02-13 08:56, Michal Čihař a écrit :
Well neither is "scripts" :-). Anybody has better idea?
install-scripts ?
Well I was rather thinking about having one place for examples and SQL scripts.
And I don't like long directory names :-).
Looking at scripts there are still some ancient perl things - anybody has idea whether convertcfg.pl and upgrade.pl are still usable?
As for convertcfg.pl I don't think we should claim we support upgrading from 2.3, I guess many things will go wrong even when config format would be fixed.
With upgrade.pl I noticed it is quite broken as it thinks that 3.4.9 is newer than 3.4.11 (tried it on git) and wants to upgrade it, that's where I stopped :-).
- -- Michal Čihař | http://cihar.com | http://blog.cihar.com
On 13/02/2012 16:31, Michal Čihař wrote:
Hi
Dne Mon, 13 Feb 2012 09:01:56 -0500 Marc Delisle marc@infomarc.info napsal(a):
Le 2012-02-13 08:56, Michal Čihař a écrit :
Well neither is "scripts" :-). Anybody has better idea?
install-scripts ?
Well I was rather thinking about having one place for examples and SQL scripts.
examples is a good name for an example script dir like signon.php and openid.php. I would expect this kind of scripts to be in this directory. Not sure if the SQL scripts should be put in the same dir, but I can't really think of a better name.
And I don't like long directory names :-).
Looking at scripts there are still some ancient perl things - anybody has idea whether convertcfg.pl and upgrade.pl are still usable?
As for convertcfg.pl I don't think we should claim we support upgrading from 2.3, I guess many things will go wrong even when config format would be fixed.
With upgrade.pl I noticed it is quite broken as it thinks that 3.4.9 is newer than 3.4.11 (tried it on git) and wants to upgrade it, that's where I stopped :-).
Broken scripts should be removed, but I'm not sure developer scripts are needed in a release version, anyway?
Kind regards,
Dieter
Hi
Dne Mon, 13 Feb 2012 18:06:03 +0100 Dieter Adriaenssens dieter.adriaenssens@gmail.com napsal(a):
On 13/02/2012 16:31, Michal Čihař wrote:
And I don't like long directory names :-).
Looking at scripts there are still some ancient perl things - anybody has idea whether convertcfg.pl and upgrade.pl are still usable?
As for convertcfg.pl I don't think we should claim we support upgrading from 2.3, I guess many things will go wrong even when config format would be fixed.
With upgrade.pl I noticed it is quite broken as it thinks that 3.4.9 is newer than 3.4.11 (tried it on git) and wants to upgrade it, that's where I stopped :-).
Broken scripts should be removed, but I'm not sure developer scripts are needed in a release version, anyway?
Most of them are removed while creating release, I'm going to review this list as well.
Hi
Dne Tue, 14 Feb 2012 13:26:45 +0100 Michal Čihař michal@cihar.com napsal(a):
Dne Mon, 13 Feb 2012 18:06:03 +0100 Dieter Adriaenssens dieter.adriaenssens@gmail.com napsal(a):
On 13/02/2012 16:31, Michal Čihař wrote:
And I don't like long directory names :-).
Looking at scripts there are still some ancient perl things - anybody has idea whether convertcfg.pl and upgrade.pl are still usable?
As for convertcfg.pl I don't think we should claim we support upgrading from 2.3, I guess many things will go wrong even when config format would be fixed.
With upgrade.pl I noticed it is quite broken as it thinks that 3.4.9 is newer than 3.4.11 (tried it on git) and wants to upgrade it, that's where I stopped :-).
Broken scripts should be removed, but I'm not sure developer scripts are needed in a release version, anyway?
Most of them are removed while creating release, I'm going to review this list as well.
Done now - the release tarballs do not ship scripts directory at all.