[DONE] changerequest renaming glest_editor

[m0ellemeister]

Hi,

maybe you've noticed that MegGlest is now available in FreeBSD. That's cool. BUT:

I've missed a detail. Glest is also available in FreeBSD. And both of them install glest_editor in the same place. This is a conflict which is a really bad one. I think in the 3.4.0 release it will be fixed in the MegaGlest FreeBSD Port by renaming the binary glest_editor to megaglest_editor

My question is: is it possible to rename the binary glest_editor into something else like e.g. megaglest_editor or mg_editor? This might prevents conflicts on ther systems too. I think, users who have Glest installed and want to try out MegaGlest won't deinstall Gelst before installing MegaGlest.

This point will be relevant as soon as MegaGlest will be packaged and available in official distribution repositories (Debian/Ubuntu etc.)

[Omega]

They shouldn't be installed in the same place though. Megaglest should have it's own folder, as Glest is not compatible with Megaglest (and in all honesty, no reason to even keep Glest if using megaglest).

[tomreyn]

With the Filesystem Hierarchy Standard (FHS) all packaged executables go into the same search path, and thus (whether or not they are located in the exact same directory) need different and unique file names. I believe that's the issue m0ellemeister is discussing here.

[Omega]

Huh? Can you explain what is meant by that better (couldn't find any mention of it in any online documentation). Are you saying that every file on a computer needs to be... uniquely named? 

[will]

Better as in thought out by experts.

Its not like you can fight it; you have to adapt to it.  MG/GAE/Glest4 not working on FreeBSD/Linux is a bigger deal to the Glest community than to the FreeBSD/Linux community.

[m0ellemeister]

With the Filesystem Hierarchy Standard (FHS) all packaged executables go into the same search path, and thus (whether or not they are located in the exact same directory) need different and unique file names. I believe that's the issue m0ellemeister is discussing here.

Yep, you got it tomreyn.

@Omega
This does not means that every file has to be a uniquely named. But on *nix/Linux every binary is placed in e.g. /usr/bin or /usr/local/bin. On Unix like OS's no application has it's own dedicated folder (usually).
Both, Glest and MegaGlest install the same file "glest_editor" in /usr/local/bin by default. That's an issue.

I can solve this just for FreeBSD by renaming glest_editor to megaglest_editor when installing the file. But i thought it's not necessary to happen on other platforms too ;-)

[Omega]

This does not means that every file has to be a uniquely named. But on *nix/Linux every binary is placed in e.g. /usr/bin or /usr/local/bin. On Unix like OS's no application has it's own dedicated folder (usually).

I see.

I can solve this just for FreeBSD by renaming glest_editor to megaglest_editor when installing the file. But i thought it's not necessary to happen on other platforms too ;-)

It'd be best to have it renamed in the SVN then for consistency.

[m0ellemeister]

It's likely that this kind of an issue exists with other files too, for example glest.bin.

[softcoder]

Latest svn revision has all these renamed, all binaries start with megaglest_ and all scripts start with start_megaglest_

so this will make it into the release.

Thanks for pointing this out.

[m0ellemeister]

Wow, pretty fast reaction