Package Details: love-git 20241223.3a6a36e2-1

Git Clone URL: https://aur.archlinux.org/love-git.git (read-only, click to copy)
Package Base: love-git
Description: An open-source 2D game engine which uses the versatile Lua scripting language to create dynamic gaming experiences.
Upstream URL: https://love2d.org/
Licenses: zlib
Replaces: love-hg
Submitter: bartbes
Maintainer: bartbes
Last Packager: bartbes
Votes: 72
Popularity: 0.000000
First Submitted: 2020-09-12 10:12 (UTC)
Last Updated: 2024-12-24 12:32 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

giniu commented on 2011-03-28 14:51 (UTC)

I'm disowning this package, so thelinx - maintainer of two other love packages can adopt it. Have fun :)

giniu commented on 2011-03-18 21:10 (UTC)

Well, standard clone/update features of hg are used here, when you do "hg clone repo" AFAIK it gets all commits but sets to default even if it isn't latest, so it shouldn't be needed.

bartbes commented on 2011-03-18 15:58 (UTC)

It would probably be best if you run "hg checkout default", as to always build the main ('trunk') branch. Or.. is this done automagically as well?

bartbes commented on 2010-11-01 22:46 (UTC)

Oh that sounds great!

giniu commented on 2010-10-31 09:45 (UTC)

Notice, that when you install package trough package manager, like "bauerbill -S love-hg", it gets installed from this package page, but later when you check what version is installed using for example "pacman -Qs love-hg", you will see "local/love-hg 431-1". Also, if you update packages using "bauerbill -Syu" it does not get updated, unless you specify "--devel" flag, when latest version of love-hg is pulled. On the other hand if I want to force update on all users that installed it because of bug for example or some other change, I can bump version here, which forces update without "--devel" if someone installed lower version than above. It makes sense really, when you get used to it - for sure it's far easier and works better than making .deb-s :P

bartbes commented on 2010-10-31 09:28 (UTC)

That is... a weird system, but sure if it follow the rules.

giniu commented on 2010-10-30 20:37 (UTC)

Hi Bart! This package is built along with Arch guidelines for hg packages ( https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines ), which means always take latest :) The version isn't really important, it's just information when the package was made. As far as I know all *-hg, *-git, *-svn etc packages work like that.

bartbes commented on 2010-10-30 20:23 (UTC)

I see you're always using the latest revision of the repo, regardless of the version of the package, you should do hg update <revision-number> to go to the revision belonging to this version, otherwise, keep it up!

giniu commented on 2010-09-27 16:16 (UTC)

One more update, added some build process description - also, fixed version information to be "$hash-$date" like in original beta distribution, instead of string "HEAD" - code to generate version information taken from ./platform/autobuild, but only parts of it (autobuild script is made to create tarballs and deb packages only).

giniu commented on 2010-09-27 15:48 (UTC)

Small update, cleaned up dependencies to make sure all but only really required packages are added.

« First ‹ Previous 1 2 3 4 Next › Last »