| 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.21 |
| First Submitted: | 2023-01-17 01:12 (UTC) |
| Last Updated: | 2024-04-16 13:38 (UTC) |
Recently, some buttons like "keyboard shortcuts" or "preferences" have been moved to the "global bar". Except that I don't get any global bar at this time. Now a part of the software is inaccessible. What is the problem exactly ?
EDIT : I am an idiot, the menu was hidden and I only had to press CTRL+H to make it appear. I have no idea why it was hidden by default though.
Please consult with known people: Comp is updated today, and rdarktable too... But
yay -Ss rdarktable-git aur/rdarktable-git v0.0.0.r187.g70c875b2d-2 (+4 0.06) (Installed: v0.0.0.r215.g06cd53f71-1) Aurélien Pierre's Ansel fork of the darktable camera raw editor/asset manager
and tomorrow it will be updated.
This is a -git package, and so it follows the master branch. In the upstream, the nightly builds have all been renumbered to version 0.0.0.
After the upstream made some changes to allow Ansel to coexist with darktable, I have updated this package to remove the "conflicts with" darktable flag. ultimately this package should be renamed form rdarktable-git to ansel-git, and I'll look into making this happen.
Fuck!!! What version I have installed with last update???
$ ansel --version this is ansel 0.0.0+187~g70c875b2d copyright (c) 2009-2023 johannes hanika
Why yay say there is version 3.9 but install version 0.0?????
Now it's called ansel… https://github.com/aurelienpierreeng/ansel
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.
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.
Should the package name be r-darktable to match the GitHub Repo name?
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
-gitpackage:-gitpackage does not have a fixed version tag, instead it will always checkout the latest master commit when you re-run the build command (for examplemakepkg -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.