Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AUR-Support/PKGBUILD #36

Open
Shadowphoenix opened this issue Jun 18, 2022 · 9 comments
Open

AUR-Support/PKGBUILD #36

Shadowphoenix opened this issue Jun 18, 2022 · 9 comments

Comments

@Shadowphoenix
Copy link

Thread to discuss and note down stepstones and advancements in creation of a PKGBUILD for the AUR

@Shadowphoenix
Copy link
Author

image

^this would be the general layout of a pkgbuild, found here: https://itsfoss.com/create-pkgbuild/

what i see a lot on the AUR is one known-to-be-stable release as a bin (like the package provided by you on your mediafire), for example called foo-bin and another one that builds from the latest available masterbranch-sourcecode-Version, for example named foo-git.

Since i havent really seen Versionated Full Releases on this Repo i will take a guess that you release sourcecode as Rolling-Release right?

In that case, AUR-building from sourcecode doesnt really make sense imo as you would really not be able to distinguish between different versions of the sourcecode.

Thats why i would say if you intend to rolling-Release the sourcecode instead to build a PKGBUILD around a bin-version. Only hosting a bin and updating that one every once in a while when you added major changes allows to distinguish old vs new Versions i think (oh that bin is of higher version than what i use, lets update)

This is something you as the owner of the source should decide as i have no clue what your release-plans regarding this project are.

(My wording might be a bit clumsy, im sleepy as hell lol)

@Shadowphoenix
Copy link
Author

this could be a rough idea of a PKGBUILD based on a binary, its still untested ofc

pkgname="Mlfc"
pkgver="$VERSIONOFBINARY"
pkgrel="$VERSIONOFPKGBUILD"
pkgdesc="DragonCenter-esque GUI to control Fanspeed on MSI Laptops"
arch=("x_86_64")
makedepends=('git')
source=("https://github.com/marshevms/mlfc/releases/download/${pkgver}/Mlfc-${pkgver}-Arch_Linux_x86_64.pkg.tar.zst")
noextract=('Mlfc-${pkgver}-Arch_Linux_x86_64.pkg.tar.zst')
sha512sums=("SKIP")

package() {

install $pkgdir/Mlfc-${pkgver}-Arch_Linux_x86_64.pkg.tar.zst

}

where do you want the binarys to be? mediafire, github,... will require diffrent dependencies to grab it, like git or wget.

@marshevms
Copy link
Owner

marshevms commented Jun 18, 2022

I think for the first PKGBUILD based on binary files is a good idea, because we have a lot of dependencies. I can add archive to my release https://github.com/marshevms/mlfc/releases/tag/0.5.2. But you must to know where to put these files.

@marshevms
Copy link
Owner

I added it. Unzip the folder and imagine that this folder is root. This is how these files should be located on your laptop. Ignore DEBIAN folder.

@Shadowphoenix
Copy link
Author

great - will take a look at specifics in the coming week starting tomorrow evening.

@fawqsir
Copy link

fawqsir commented Jul 14, 2022

Just wondering on an update? I am excited for this to be in an aur. hopefully the Chaotic-Aur.

@marshevms
Copy link
Owner

@Shadowphoenix how it's going?

@Shadowphoenix
Copy link
Author

sadly i was relatively busy the last month, im currently working on this and have a somewhat working PKGBUILD but it errored out on me once during testing so im trying to figure out if that was on me or the script. will try to get this completed by Sunday.

@Shadowphoenix
Copy link
Author

whoops. i forgor xD i will get back to this is in the near future - although i will have to start from scratch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants