Package Details: ansel-git 0.0.0.r1246.ga665765ed-1

Git Clone URL: https://aur.archlinux.org/ansel-git.git (read-only, click to copy)
Package Base: ansel-git
Description: Ansel is an open-source photo-editing software for digital artists, designed to help you achieve your own interpretation of raw digital photographs.
Upstream URL: https://ansel.photos/
Licenses: GPL3
Conflicts: ansel
Provides: ansel
Submitter: AlynxZhou
Maintainer: AlynxZhou
Last Packager: AlynxZhou
Votes: 10
Popularity: 0.052627
First Submitted: 2023-01-17 01:12 (UTC)
Last Updated: 2025-02-05 02:04 (UTC)

Pinned Comments

AlynxZhou commented on 2024-01-03 11:36 (UTC) (edited on 2024-01-03 11:37 (UTC) by AlynxZhou)

For people who are not familiar with AUR and -git package:

-git package does not have a fixed version tag, instead it will always checkout the latest master commit when you re-run the build command (for example makepkg -sif). Considering the Ansel upstream is actively refactoring, you may need to re-run the build command to get the latest commit when you get some problem.

PKGBUILD here only needs to be updated if there are changes of building steps, so the "Last Updated" doesn't mean the version of software you could build.

Don't bother upstream devs with words like "the AUR package ansel-git is last updated at 1 week/1 month ago please update it to latest commit" in GitHub issues or Matrix chatroom, I've explained that only thing you need to do is to re-build the package.

However, if you are really sure there are problems in the PKGBUILD, feel free to comment HERE, because upstream devs may not be a Arch user and they don't maintain this PKGBUILD. I'll try to fix it.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7

AlynxZhou commented on 2022-10-24 15:13 (UTC)

Hi, my question is not about binary or directories name, I mean if the github repo is named to r-darktable, when user searches it on AUR they'll use r-darktable, but this PKGBUILD is called rdarktable so it won't show. Should we use r-darktable for this PKGBUILD? Thanks.

mmaguire commented on 2022-09-11 02:15 (UTC)

This package is a mutually exclusive alternative to the darktable package. The build scripts are hard-coded with the name "darktable" for the binary and library directories. To quote from the developer's build instructions:

R&Darktable uses the same scripts and building stack as upstream darktable, so everything works the same but you need to be aware that it will get installed in place of darktable and as darktable, so it uses the same pathes and default config/database directories. The CLI commands are all the same and R&Darktable will be registered as darktable as far as your OS is concerned.

I'm not sure at this point if it's worth it or even desirable to have it installed somewhere else and using different config pathes and CLI commands.

So, it we want to package this as a separate package, some downstream patches would be required. Since this is really just an interim fork until vkdt becomes more mature, it is probably not worth the effort.

I made this package so that I could easily use this as the main darktable package for my system that could easily be updated. If I want to see what is happening with the main darktable project, then I build that separately under a different directory tree. Therefore, I recommend you make a decision as to whether you want to use darktable or rdarktable as your official package, and just install the appropriate one, and if you want to explore the other variant, then build it somewhere under your home directory as you normally would for a development build.

AlynxZhou commented on 2022-08-16 11:51 (UTC)

Should the package name be r-darktable to match the GitHub Repo name?

« First ‹ Previous 1 2 3 4 5 6 7