Deletion is good a solution as any. I was installing this file as documentation in my RPM, but putting executable files in /usr/share/doc is allegedly poor ettiquete...
On Mon, Mar 31, 2008 at 4:27 PM, Reinhard Mueller <[EMAIL PROTECTED]> wrote: > Am Donnerstag, den 27.03.2008, 09:22 +0100 schrieb kilo: >> In fact I've never ever used gnue-diag.sh before... > > Neither have I. The script also seems to be unmaintained for at least 5 > years. > > If we decided to keep it at all, I would prefer if we used something > like > > echo "from gnue import paths; print paths.config" | python > > to find out the directory with configuration files rather than > hardcoding it. However, I actually doubt the usefulness of a script that > types out a config file... > > If anybody has used this script within the last 3 years, please speak > up. Otherwise I would propose to remove it. > > Thanks, > Reinhard _______________________________________________ Gnue-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnue-dev
