Page 3 of 3

Re: An ongoing problem for löve distribution.

Posted: Fri Jul 11, 2014 1:25 am
by Inny
Ubuntu has these documents that explains how to bundle software into a deb: http://packaging.ubuntu.com/html/packag ... tware.html and https://help.ubuntu.com/community/UpdatingADeb

I've never made a deb, so I can't offer any more help. I have made RPMs before. I recommend you do not try to make RPMs.

Re: An ongoing problem for löve distribution.

Posted: Fri Jul 11, 2014 5:20 am
by josefnpat
Inny wrote:Ubuntu has these documents that explains how to bundle software into a deb: http://packaging.ubuntu.com/html/packag ... tware.html and https://help.ubuntu.com/community/UpdatingADeb

I've never made a deb, so I can't offer any more help. I have made RPMs before. I recommend you do not try to make RPMs.
I have a script for debs, but it's really hacky, so I'm not interested in supporting it. Hit me up with a PM if you want a copy.

As for RPM's, they aren't that bad, just a bit more CLI than debs. SRPM's are where it's at though :3 Gotta find a 0.9.x one though ...


edit: this looks promising; http://rpm.pbone.net/index.php3/stat/3/ ... a5.src.rpm

Re: An ongoing problem for löve distribution.

Posted: Fri Jul 11, 2014 11:29 pm
by BozoDel
Wine is sometimes able to run Windows löve games but sometimes it isn't. Can't remember an example, but trust me. In any case, that's only an interesting idea for those overzealous about source code.

josefnpat's idea seemed like the ultimate solution... except that, what are the odds of zenity being installed by default on a KDE environment?

Re: An ongoing problem for löve distribution.

Posted: Sat Jul 12, 2014 9:09 am
by murks
One real issue with Löve on Linux is version incompatibility. For example I tried to play Super Mari0, but it was written for 0.8.* while my distributio provides 0.9.1 by now. There still is a 0.8 package though, so it's not such a big issue. But what about 'slow' or 'stable' distributions that will still provide 0.9.1 when 0.10.1 is out?
On Windows and OSX you just ship the right version, but can you get this to work reliably on Linux?

Re: An ongoing problem for löve distribution.

Posted: Sat Jul 12, 2014 10:02 pm
by dusoft
Ensayia wrote:There is no single way to make a binary package that works on all Linux distributions, that's why it hasn't been done.
Yes, there is: .bin packages or .sh scripts that take care of everything else.

Re: An ongoing problem for löve distribution.

Posted: Sun Jul 13, 2014 3:11 am
by clofresh
You guys should check out fpm, a script that abstracts the creation of rpms and debs.

Code: Select all

# Install the fpm gem (requires rubygems)
sudo gem install fpm

# Generate an rpm from a directory
fpm -s dir -t rpm -n mygame -v 1.0 -C /path/to/mygame

# Generate a deb from a directory
fpm -s dir -t deb -n mygame -v 1.0 -C /path/to/mygame

Re: An ongoing problem for löve distribution.

Posted: Sun Jul 13, 2014 5:38 am
by josefnpat
BozoDel wrote:Wine is sometimes able to run Windows löve games but sometimes it isn't. Can't remember an example, but trust me. In any case, that's only an interesting idea for those overzealous about source code.

josefnpat's idea seemed like the ultimate solution... except that, what are the odds of zenity being installed by default on a KDE environment?
It falls back to an error when run in a cli. You could also add a fallback with xmessage.
clofresh wrote:You guys should check out fpm, a script that abstracts the creation of rpms and debs.
This I will check out!

Re: An ongoing problem for löve distribution.

Posted: Fri Jul 25, 2014 9:40 pm
by socketubs
There is a related topic here: http://love2d.org/forums/viewtopic.php?f=4&t=12106

My opinion quoted from other topic:
Sorry for reviving this dead topic. But is Linux distribution in same state as previous posts ?
Cause I think, current state is nearly broken for Linux.

Creating .love is cool when you are in a devel process or to share with your friends, but if you want to sell your game, I don't think you can rely on this method. Because you just can't ask all linux users that have the chance to have ppa to add it, and install love. This is not very acceptable.
Creating .deb or .rpm packages don't allow you to have games with two differents love2d versions on the same system. This is problematic for a isolated distribution.

Is it possible to statically compile love2D (I have no very much compiling experience) ?
Is it possible to embed shared libs like Windows in a package ?

I have done a little hacky python script that retrieve via ldd libraries and create a launcher, https://gist.github.com/socketubs/de78d7d5eeebcdd7642f
It works on some distribution but I have no idea if it's a correct method.
You can follow some of this work here: https://github.com/MisterDA/love-release/issues/7

Re: An ongoing problem for löve distribution.

Posted: Fri Jul 25, 2014 9:54 pm
by murks
It is possible to have multiple versions installed through package management. Arch Linux currently has a package for 0.9 and 0.8: https://www.archlinux.org/packages/?q=love and there are older versions available through the user repository. I'm pretty sure you can do this on .deb or .rpm based systems as well.

Of course it would still be somewhat nicer to just click on some icon without the need to install anything.

Re: An ongoing problem for löve distribution.

Posted: Mon Jul 28, 2014 10:25 am
by socketubs
It is possible to have multiple versions installed through package management. Arch Linux currently has a package for 0.9 and 0.8: https://www.archlinux.org/packages/?q=love and there are older versions available through the user repository. I'm pretty sure you can do this on .deb or .rpm based systems as well.
It's an interesting way to distribute game. I think it could be the best on Linux but for now, all love package in the PPA are named love.
Maybe actual ppa could be updated to use a better love name for packages ?

I think other solution could be https://github.com/ValveSoftware/steam-runtime (steam-runtime).
I've tried to compile love against this run-time environment but for now it's a failure for me.