Package Details: feedthebeast-classic 1.5.1-3

Git Clone URL: https://aur.archlinux.org/feedthebeast-classic.git (read-only, click to copy)
Package Base: feedthebeast-classic
Description: Feed The Beast offers many different styles of Minecraft modpacks to the community, catering to all tastes.
Upstream URL: https://feed-the-beast.com/
Licenses: Apache
Submitter: Nayla
Maintainer: Nayla
Last Packager: Nayla
Votes: 45
Popularity: 0.000000
First Submitted: 2020-10-16 12:06 (UTC)
Last Updated: 2020-11-26 15:56 (UTC)

Dependencies (6)

Required by (0)

Sources (2)

Pinned Comments

alissonlauffer commented on 2020-04-09 03:53 (UTC) (edited on 2020-04-27 08:03 (UTC) by alissonlauffer)

Hello guys, I know you are waiting for the new FTB update, but for now packaging it is not possible, since the launcher cannot be installed in places that the user does not have write permission (E.g: /usr/share/feedthebeast or /opt/feedthebeast). Check this and this. For now use the classic launcher or install the new one using the official installer at https://feed-the-beast.com.

Also: When packaging the launcher is possible again, I will create another package for the classic/legacy version (for those who prefer to use it).

Latest Comments

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 Next › Last »

justin8 commented on 2013-12-29 10:01 (UTC)

Please either add a dependency on extra/desktop-file-utils or move the desktop file manually. This fails to build in a clean chroot.

koromerzhin commented on 2013-12-12 10:40 (UTC)

Replace c1772718bfec5a2e12d7e8383be0ab1addabbbed8859d5c20033bcc3b8912420 by 47c970d7089fd05f38737c40b8bc004969c4e5c76a63272d83a5b098da88c6ee and ea6ab84f2fdafb0689cc7520665e6aa093145af5a2cc5e8c11dcfb530a30e892cbe5715c66a33f12d6858207c3dea6b85403ba239e36b39bf5bf9525c3580582 by 4e67d184c06c15bc981b17b6a297885c505b778e529f5da0a6317c3e2b3a77b392c767b4ea1e35aae7b29104a0181b1ebc31ef7a956015addc5f2f241251d68d

Tanath commented on 2013-09-22 23:57 (UTC)

MD5 is broken. It is not useful for verifying integrity, and should not be used.

luolimao commented on 2013-07-25 14:21 (UTC)

Yeah, that's because the launcher was updated from 1.2.5 to 1.2.6. Just flag it next time, thanks.

twighk commented on 2013-07-22 12:55 (UTC)

Hi, I think the checksums for the launcher.jar should be 06de893b7040d542ce54b52f9731ca2ad552e5cf89d42ebbabbfe514e66767f4 and 4b21573db23096860169d6ef07c08d3fa98dd4f4ac319f94eefbee8c057197fb78d30504e2a388fa9dcda520300d30228580993e4d17902c6b12a0b05df19ddc , for the sha256sum and sha512sum, respectively.

smp commented on 2013-03-08 13:39 (UTC)

I too am for replacing the two checksums with only one (whichever type). But although MD5 has been superseded by the SHA algorithms I see no reason to stop using it for verifying the integrity of a download.

ASzc commented on 2013-03-08 00:12 (UTC)

If I may propose a comprise on the checksum issue, maybe pick one of the two existing types and use only that one type? I wouldn't be in favour of replacing them with MD5, since that that algorithm has been superseded by SHA-1, the SHA-2's and now SHA-3. Regarding the URL hash component, what is certain is it is there to prevent the URL from being stable for over more than a day. I don't think its there for the purposes of driving traffic to the site though, as the download only needs to be done once, and then the launcher takes over. I think this may just be a feature implemented by creeperrepo.net as standard hot-link protection for all their clients; FTB just happens to be a client of theirs.

smp commented on 2013-03-07 15:08 (UTC)

I understand that the time difference is small time but having *two* checksums looks really odd. And regarding upstream changing the URL, I think that they change the direct URL every day so they can prevent people from directly linking the files. It seems that they want to make people either visit the Feed the Beast site to download the launcher or use the link which displays adds and makes you wait a few seconds before you can download. That would explain why upstream ignored your email (if they even read it).

luolimao commented on 2013-03-07 14:55 (UTC)

This reduces the "browse upstream website => copy/paste url => check checksums" to a mere "check checksums" step, so it's easier to check if stuff has changed. Also, I didn't know that the code was open-source until ASzc mentioned it, much less where the code was hosted. Anyway, I'll update the license when I get back. Regarding the checksums, really? I mean, you're complaining about wasted *milliseconds* here. Go ahead, time it yourself. I did: https://gist.github.com/luolimao/5108569

smp commented on 2013-03-07 14:32 (UTC)

It's nice to see that the method of generating the URL link was found. Though I don't see how this makes you more aware of changes upstream. Please note that during updates which don't change the built package - such as only updating the download URL - the pkgrel shouldn't be changed. Then the PKGBUILD definitely shouldn't have two checksums for every file. One is enough as having multiple causes makepkg to check the checksums twice. Then you should consider using md5 sums because using sha2 sums in this case doesn't introduce any benefits, the sha2 sum just takes more time to generate (and the string is longer, cluttering the PKGBUILD). Finally the license should be updated to 'Apache License, Version 2.0' as stated on the upstream URL.

« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 Next › Last »