Package Details: vkbasalt 0.3.2.4-1

Git Clone URL: https://aur.archlinux.org/vkbasalt.git (read-only, click to copy)
Package Base: vkbasalt
Description: A Vulkan post-processing layer. Some of the effects are CAS, FXAA, SMAA, deband.
Upstream URL: https://github.com/DadSchoorse/vkBasalt
Licenses: zlib
Submitter: gee
Maintainer: gee
Last Packager: gee
Votes: 22
Popularity: 2.67
First Submitted: 2019-10-21 10:32
Last Updated: 2021-01-24 23:31

Latest Comments

1 2 3 4 5 6 Next › Last »

yochananmarqos commented on 2020-11-07 01:10

@gee: I still think you're missing something. Whether the PKGBUILD is split or not does not change the packages themselves. The dependencies will not change, there's no transition at all. Since they won't change, you could split them apart with no pkgrel() bump because the build process did not change.

gee commented on 2020-11-07 00:55

@yochananmarqos: yeah I'm more nuanced about this than you... I understand your point, and live by it to an extent, but I don't want to break functionality and waste users' time if it can be prevented. Of course, this is also AUR, not quite the best place for people that don't want to read.

So what I think I'll do is either: - give it about a week and do it, and add a note in the post-install step for 64b. - do it right away but make the dependencies circular for a week or so before removing that.

Since I'd rather not do extra work, I'll probably go with the first. Anyway, we've both spent too much time on this topic already, it is not worth it. :)

Yeah, I still think makepkg should support split package for archs, if not it's just full of redundant stuff for no reason...

yochananmarqos commented on 2020-11-06 23:15

@gee: We're package maintainers, not hand-holders. It's not up to use to write them a tutorial. That's what the upstream README is for. All the other lib32- packages in the Arch repos are separate packages.

I originally thought it would be easier to maintain as a split package since mangohud-git was, but you helped me realize it's not the greatest idea in the world to mix different architecture packages together.

gee commented on 2020-11-06 22:23

@yochananmarqos: Hmmm I am not sure we are talking about the same thing. What I mean is that if I split this vkBasalt page (/PKGBUILD) from being a single package to having the 32b on a different page (/PKGBUILD), I'm afraid some people will see not understand why things don't work with 32b games anymore unless they manually grab the 32b PKGBUILD too. I'm talking about a single package because some people may have not yet grabbed the 32/64b package split yet, which is transparent indeed, and which is what I'm hoping will allow a smoother transition if given time.

yochananmarqos commented on 2020-11-06 22:15

@gee: Again, the split package is transparent. They'll still see the update no matter if the packages are split or not.

gee commented on 2020-11-06 22:10

@yochananmarqos: Sad :/ I guess I'll wait a little bit for people to get the current update that'll give them the 32b before doing the proper split then which hopefully should be straightforward then.

Thank you for your help!

yochananmarqos commented on 2020-11-06 21:51

@gee: No, they'll only appear together when they're part of a split package. Other than this page, split packages are normally transparent to the user, anyway. Just list vkbasalt as a dependency of lib32-vkbasalt as is common for packages like these.

gee commented on 2020-11-06 20:03

@yochananmarqos: Cool! Is there a way to somehow keep this page connected to the lib32 one with such a split? I don't want people in the future to update vkBasaslt and lose the 32b part and not know why... If not I may wait a few weeks before making this transition.

But yeah, like you I wish I could do all that in one single file, it seems clearer, and it's less stuff to download (not that this is a big software, but I want to think even here it should matter).

yochananmarqos commented on 2020-11-06 19:53

@gee: Good point, it appears Arch doesn't include different architectures in split packages. When I was Co-Maintainer for gamemode / lib32-gamemode, we had it as a split package, but the Arch community maintainer split it since he imported it. I've now split them: vkbasalt / lib32-vkbasalt

gee commented on 2020-11-05 04:45

@yochananmarqos:

  • Alright for meson install, when I started this package it had to be manually done and I never kept up with the changes.

  • Well that's for split packages built in one go, in this case we double build, once for 32b and once for 64b, all that is shared is the initial source, similarly to how split the mesa and lib32-mesa sources are.

I'd be happy to have the rest of your comments when you have the time.

Thank you!