AUR (en) - shadered-git

Search Criteria

Package Details: shadered-git 1.5.6+2.g780e96791f-1

Git Clone URL:	https://aur.archlinux.org/shadered-git.git (read-only, click to copy)
Package Base:	shadered-git
Description:	Lightweight tool for creating and testing HLSL and GLSL shaders.
Upstream URL:	https://github.com/dfranx/SHADERed
Licenses:	MIT
Conflicts:	shadered
Provides:	shadered
Submitter:	Emeric
Maintainer:	Emeric
Last Packager:	1ace
Votes:	2
Popularity:	0.000000
First Submitted:	2019-10-23 11:36 (UTC)
Last Updated:	2022-11-03 10:19 (UTC)

Git Clone URL:

https://aur.archlinux.org/shadered-git.git (read-only, click to copy)

Package Base:

shadered-git

Description:

Lightweight tool for creating and testing HLSL and GLSL shaders.

Upstream URL:

https://github.com/dfranx/SHADERed

Licenses:

MIT

Conflicts:

shadered

Provides:

shadered

Submitter:

Emeric

Maintainer:

Emeric

Last Packager:

1ace

Votes:

Popularity:

0.000000

First Submitted:

2019-10-23 11:36 (UTC)

Last Updated:

2022-11-03 10:19 (UTC)

Latest Comments

oysstu commented on 2020-02-28 07:46 (UTC)

Thanks, I'll try the non-git version. Obviously, downloading the sources through git is the way to go here. The only downside is not being able to compute checksums. The -git packages are typically used for development packages (i.e. master branch) or upstream sources without releases/tags, which was the point of my previous comment.

Emeric commented on 2020-02-27 19:24 (UTC)

I just did a package for the 1.3, and updated this one not to conflict with it.

Let me know if that works for you!

Emeric commented on 2020-02-27 18:39 (UTC)

Yes you were right to mention it ;-)

I think I can do a version with a fixed GIT commit, it would track releases but still use GIT.

Tracking only github releases would be very difficult ATM, because the package relies heavily on git submodules (which are not easily available with the releases packages) and not on shared dependencies like we usually do. Changing the build system to work with shared dependencies would be a bit of work involving the software creator, and testing on all supported platforms... Wich at the moment I have no intention to do ^^ but that would be cool!

oysstu commented on 2020-02-27 18:09 (UTC)

I figured it was an upstream issue, just thought I'd mention it. Have you considered making a non-git package for this, tracking the releases/tags on Github? Seems like the new releases are made frequently enough.