You are not logged in.

#1 2015-08-10 03:24:53

csolisr
Member
From: Costa Rica
Registered: 2012-06-10
Posts: 23
Website

[Request] SFXR, a package I adopted and couldn't port to AUR4 on time

Once upon a time, I had adopted an orphaned package named SFXR. It's technically abandoned, but the later version, BFXR, requires non-free software (Flash) to compile and run. The problem is that I only had enough technical know-how to modify the variables needed to keep SFXR up to date, and nothing else. Later, I received the warning that all AUR3 packages were about to migrate to AUR4, which meant that I had to supply a personal, stable repository to upload the MAKEPKG, and also I had to learn how to rewrite the MAKEPKG by hand. I had no way to do either, and now that the migration has occurred, not only has the MAKEPKG been deleted from the Internet, but also all the guides required to rewrite the MAKEPKG in the new format required by AUR4. Would someone kindly help to port SFXR back to AUR4, or am I supposed to learn AUR4 by myself?

Homepage of the package: http://www.drpetter.se/project_sfxr.html
GIT repository (does not include the MAKEPKG because the program is not written by me): https://github.com/grimfang4/sfxr

pkgname=sfxr
pkgdesc="Sound effect generator"
url="https://github.com/grimfang4/sfxr"
license=('MIT')

(All other data lost with the deletion of the original MAKEPKG)

UPDATE: I found that someone has made a backup of AUR3, so I was able to recover the old files. However, with the guides to port AUR3 packages to AUR4 gone, I still am unable to port them myself. The files are located at:

https://github.com/felixonmars/aur-mirr … aster/sfxr

Last edited by csolisr (2015-08-10 03:37:39)

Offline

#2 2015-08-10 06:53:59

severach
Member
Registered: 2015-05-23
Posts: 198

Re: [Request] SFXR, a package I adopted and couldn't port to AUR4 on time

PKGBUILD is the file. makepkg is the program that works PKGBUILD to produce the package. MAKEPKG isn't anything in particular.

AUR4 didn't change the PKGBUILD format. Other than versions, the main thing that needs fixing in old packages is old techniques that are no longer allowed.

There you go. You're an alternate maintainer so you can update.

For easy migration and new package submission, try my git-aurcheck in the AUR. It flags many of the old techniques and leads you through the git labyrinth to a successful submission.

Offline

Board footer

Powered by FluxBB