[Phpmyadmin-devel] Moving all end user scripts to examples dir
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. -- Michal Čihař | http://cihar.com | http://blog.cihar.com
-----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 SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPORQaAAoJEP78ZdGBr2RKJMwP/RyMvYglXBo83sfH1RD+dv2K iWIhWi7GsggBy0T3Ea8+N0BKSaayKX5ZBkMC1cPtMIXnDB9eA8tisQVKfv0KyKad q4SPC0KGyxxvsUjSdGAK7Wva18mQc7itpZU59XoLedfaPXlAw0WcY+n84qEKrCxU qA8d+32ZRFMHrrpndc1IF/b5comp9Xp+Sik+enrcVIBGcBupexq3NX48GUscE+oX PF0oQ1kWw4TSIjPDMUbz+nyOVzxgaKWhI6WyxKedeZPmuMvgJ5SvpIEcS/Pf20JT o2zf46uTq7kEtJXeN6FxIWlYtMuQP6mJk6D9TaG0q2WFsA9LDG+4IuNNkTLKFsl5 T45QatIjqWAKRiychTHPA0BWqjCF2ZuHC7xu5gyG2CtBzjfvTo/FJAG3cstHUnip 5kXTBz6FsqBWHm8nDg2ESYNJG8PAGdHhdBheiISyO84lLMurjS3IQ2OLmiUdExkO aZgqoTqa2f4g0Pf7D3iG0/wRDhYdtsGu87j98ZVTJ6HIbwp6hZuwMUxlfFVU37Rk qyjXjn4JPCDhtiqfBM3hICR+XRnz3ig15N9c+FOesqiS3iAVHeJGd7WkE9AJMPxC 6vm4tTGRO9pyvLgGhig84jVsrchnH/BmsWZkOmKkoRuWesGsuE+Pxv4o35pXXYcK tRdzVyAqR45Nr6fosOir =67ig -----END PGP SIGNATURE-----
-----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 SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iQIcBAEBCAAGBQJPORaTAAoJEGo39bHX+xdNwGoP/0dmSGQ48afgE13OSQX79vvF IKOEtRsWtiCFsPBEIqe0mqUUW/0HcWVfp+YjRoLzMG16mIID/Fs15BWUOI6DFSHo MI3M7S/0iAIzp0LZcY3SN59gpJqyhnc0d2sFrUHr8mYQIbB71ff1kg1+t6tJpU0Y RF0zHILDP3ilzWjn0s3nTQv2qy60hJ4fCEJS2iZoui+//D8e+tWDUqrH0uS7Ohwv 7pYeXY0LrkVfN+IBLdBg1dl6GzFmy4FFleHEjCWEEmM6Ccbrxmy9cn8VrhC4wTlj sdbj1MWg1qFTRo4KiyQ3Lkdm1ANiZgKwrWXPv/FAXS3rM4IW4dTBpkIWyPwYCg34 XN8UqMBJsy7IrsTUImOnh6mb4jyYNErDE+1e0UAKfC+ek4LXzvn8MCmv+N0QsGya EeMbJWUOrNRwcO+YqVBE9ITUvW7hziq52RdH8TcDfyJEIBDrf7kgmegds1xL0xg+ n090f4sdlHnj7KgbXxwI7ENu98VEduaSSzN7Vj7a/X1GAOqQBhFK0QJAkEA/dbiU PaNqQNU0YUGvu4LcFSESAEtsjzkmUGA29csYqxrmBLHDywA27acGZFe2dIIrEr6e gsS3ofBvbNrqhyIsyXLEBkKdQkqWtf1Q35XdE5aOZY63ACXB0/+YoqtjkOJCgI9k Cz1SXHfHkgXkpJkbI2IV =pzqD -----END PGP SIGNATURE-----
-----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 SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPORfUAAoJEP78ZdGBr2RK/kYP/R49j23Z+ALeSc62Vlq3vQ1N 0D9N1qf/HhKwdGZeTbS+p25g8PFO5VK7q0IFfzjB/bUuYdtWuUoVAjlhp0StBOTL wUe+YNNn8raxfqfxf2KIT+l0SAQ9e26U42bU0Va9uBwoxE826tolEZ2reJsjKE1N jHZkOO1QAiMmtkxezdZdwZQpdPlU6a/SIF/qKf/vR2sKNfRAQE7W3TrUIe/H7hNs Nzar/M1gsB/5UgSEUfHAF/jbrudADIqkKHKqiN5wbBTEuBmhLgUXvEmFTygezASR HeKN2bi+OyDDprOi+bDFAdaVlgrvIYmmZepYEWhnxuX9CVefSUuVwutU35vdsvsB 6YDIJ3E0rvSt/ckKOQW9rUg74AdTx8n7xDwsEHWWNH3n8GByJZsaLCzukektchhC +fjEBxUo/Kh3Vrz3uEBR3zTTfoLSTLLjBpGwYh4oWIqUS3ZiliJqYhCDvs8W41NR IvL9boVBGTimyBB+vt600rXM7ZrbMY8O/Ks4rEF/Q6CQU+jpE0nEOgWLyGVE5yrS SaDPR2m4dzYv3gTPbu85JwXxuD0R9MTdJ9hksN5AjyI1aBbnBnUJNfXwk7ph4VfY X/Feog4qr2DX411XYYQpak0F3AZXgyHH8Ro9Fd9jSMP/1Xd1iivqs/3lwnjWU3e2 f1qm+/vBz0AgCWrVwbrH =gWh1 -----END PGP SIGNATURE-----
-----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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iQIcBAEBCAAGBQJPOSy4AAoJEGo39bHX+xdNV+0P/jXtMqpO2Z+qqO7nlb108p1M 0X+7FaSwErNKYuz42X0A1G24bbEZb8rZt98C7h/lUnEWHJK4GGxq9TRDH2UTHmc+ szO45FmgRXQwXBRlT3wPOA7A4pmRqHDSmwLT54BlR8jJ95eSOUaxKMTbcL0p47Si NdqK621+rQxrce8rHXhwvEcPjIjTVXM4jN3T20Mkzbd4qVNd3/NoPeCYIYo4U816 o0p0M6e6JDQyjVMLvUbq/BUQZ2pxOVKNNDeJqq8DztRZuTK89P9IPrSHShZTHtnS XcDGLl8PgcsERHkAMouSlZ0w6Km+WiLUNivFhBuXOz9fLBgp+bUp2M8bbAW1nLS5 FHEIsO00uf+onqHNNRp79xifmWmp1OwREy+lEg1s4+vObeFRRseQbCPwPHEOCJpj OOTGP47r8tl3pc3l3UgIcloECbPcaQCZOhgFPCT2VBbpqxTDmDGiD1VD5n+dhUcj g0RtgQHXxUQii2O2jEYiX5U4Yvoql+JMPLLMPSJMMkwPkXPZXptOk2ZbctJwa8Ee O4FOhk6rTYYiIbqvaxne/5arXAiEVcSCCIQMKHk7PTfaCbflr5XZa4O3AV4TRmaI X9qICDUmCgnLXCTb/pcHTAOrGtHyPxRfkgPMs+ZyevUFtjdZxfqfaMoYeHFlGlBa k0lJgMFAATLagFqb9Qw/ =spTb -----END PGP SIGNATURE-----
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. -- Michal Čihař | http://cihar.com | http://blog.cihar.com
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. -- Michal Čihař | http://cihar.com | http://blog.cihar.com
participants (3)
-
Dieter Adriaenssens -
Marc Delisle -
Michal Čihař