Package Details: minfetch 1.2.1-0

Git Clone URL: https://aur.archlinux.org/minfetch.git (read-only, click to copy)
Package Base: minfetch
Description: a simple customisable fetch script
Upstream URL: https://github.com/xXTacticalWaffleXx/minfetch
Licenses: GPL
Submitter: tactical-waffle
Maintainer: tactical-waffle
Last Packager: tactical-waffle
Votes: 1
Popularity: 0.000000
First Submitted: 2022-08-31 12:17 (UTC)
Last Updated: 2023-06-02 21:03 (UTC)

Latest Comments

tactical-waffle commented on 2022-10-02 05:33 (UTC)

@lmartinex-mirror

hey sry for replying so late, tbh im fine with having to update the checksum whenever i update it as i rarely do that now cause its like mostly done as for the having to upload it as a vcs package isnt that just for packages that use the vcs to get the source code

lmartinez-mirror commented on 2022-09-01 01:04 (UTC)

would that actually cause a problem as long as i keep the PKGBUILD up to date with the right checksum

You would have to constantly update the checksum for this package every time you make any sort of change to your script. It would be easier for you to just tag a release on GitHub so that the next time you release a major or minor update, you don't have to worry about anything breaking.

Packages that target the master branch have to be uploaded as VCS packages. In this case, this should've been uploaded as minfetch-git. I've already gone ahead and wrote the PKGBUILD for that, so this would have to target a stable release from upstream.

MiguelX413 commented on 2022-09-01 00:24 (UTC)

Pretty fast, pretty epic

tactical-waffle commented on 2022-09-01 00:06 (UTC)

@Lmartinez-mirror

ty for the advice, this is my first time making a package XD ill change the provides and conflicts lines rn. for the checksum thing, would that actually cause a problem as long as i keep the PKGBUILD up to date with the right checksum, the only thing i could think of that might cause an issue is if someone is using yay and they don't clean build it but i'm not totally sure how that works

lmartinez-mirror commented on 2022-08-31 17:22 (UTC)

Hi, a couple of things with this package.

  • This package will break the next time you push any sort of update to your upstream because the checksum of the script may change. You should cut a release and have this package target that instead.
  • Packages provides and conflicts themselves by default; you don't need to specify it again in the PKGBUILD.