Installer for all (>100) Linux distros

[Mike4Linux]

Hi
could we get something alike torcs:
http://torcs.sourceforge.net/index.php? ... iinstaller
Would simplify life.

[anewb]

Are you referring to the torcs:

Code: Select all

$ ./configure
$ make
$ make install


Because if so, this is pretty much standard for most thing compiled with make.

The only problem with doing things like this, tends to be it never notifies a package manager, and because of this, it may cause conflicts or problems in the long run (Like a package being installed, and replacing files put there by make)

Generally doesn't, but could do.

Not sure how FGFS is compiled though, as I've yet to try it (or need to)

[Canseco]

>100 Linux distros? It's more accurate >600,
Packages from repos or version control, is more secure and updated.

[Mike4Linux]

Are you referring to the torcs:

[code]
$ ./configure
$ make
)

No of course to: Linux Binary with Installer (1.3.0)

I'm simply getting bored by all this incompatibilities within Linux... Why not create such an installer that recognizes whatever package ( deb, rpm etc. ) manager is used.

[AndersG]

No of course to: Linux Binary with Installer (1.3.0)

I'm simply getting bored by all this incompatibilities within Linux... :? Why not create such an installer that recognizes whatever package ( deb, rpm etc. ) manager is used.

Excellent suggestion! When will you have a beta ready for testing?

/Anders

[anewb]

No of course to: Linux Binary with Installer (1.3.0)

I'm simply getting bored by all this incompatibilities within Linux... Why not create such an installer that recognizes whatever package ( deb, rpm etc. ) manager is used.

Excellent suggestion! When will you have a beta ready for testing?

/Anders

Lol.

---

Mike4Linux, the only problem with this, is the fact that there ARE so many distributions, it would be near on impossible to say "It'll work on all". Because 1. Filesystem layouts can and will be different, take a look at the filesystem's layout on Arch Linux, and then Fedora's and then uBuntu's you'll find there all different.

For example on ubuntu FG would be stored here:

/usr/share/games/FlightGear

On Fedora

/usr/share/FlightGear

not sure about arch.

- configurations may also be placed in different places per linux, for example some Linux's use a different filesystem layout and don't have an "etc" folder.

RPM & Deb, are two completely different things, and would probably be near on impossible to be compatible with each other. Not to mention these are not the only form of packages, arch uses tar for example, using "Pacman" installer, so for example install a package on Fedora: "yum install FlightGear" - ubuntu: "apt-get install FlightGear" Arch: "pacman -S Flightgear" (I think, haven't used arch in a while)

and even if you did manage to install using all the package managers. What about the ones that simply do not have a package manager? or the homebrew Linux's that are custom made by someone for them self? you'll never know how there FS is layed out without directly asking them.

This task would be VERY difficult. at least, if you want it to work on all that is.

[Mike4Linux]

Of course not all...only those that want to:
https://www.linuxfoundation.org/lsb-cert/productdir.php?by_lsb

[Tuxklok]

Just use autopackage or loki installer if you want vendor neutral packages....

[Blender3D]

I like the kind of installer Nvidia uses for their drivers very much. It works very good and is easy to use.

--Blender3D

[Tuxklok]

I like the kind of installer Nvidia uses for their drivers very much. It works very good and is easy to use.

--Blender3D

Which I believe is based on makeself, which is part of loki setup(which the makeself author also co-authored), which is what the torcs installer in question uses as well.

[mike4lin]

http://listaller.nlinux.org/

Probably we try to use this for the next FGFS Linux version?

[gluon]

Well, at least it would be nice if there were packages of the next release for the mainstream distributions available on the FG download site.
That's not that hard to produce actually since OpenSUSE has a build service website which lets you do exactly that:

http://en.opensuse.org/Build_Service