-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue #56 - Provide a way to update the darktable lensfun database #57
Conversation
Why not just copy the db from a more recent upstream git commit, if you want to stay with the old release? |
From
Hence we shouldn't rely on what's in git. |
If you compare the database in both versions (0.3.95 and git HEAD), you see, that all files still have the same version: The last version bump was 1 Jan 2016: |
But what about the future? What if tomorrow they bump it? |
Then we will just switch to git master? |
@eszlari we don't want to buld git master though. |
No, unless upstream does it. The lack of recent release of lensfun and the fact that Darktable uses 0.3.95 (which, I read, was not the best idea) is already suboptimal. |
Does it actually make a difference in practice? Is it unstable / buggy? There are other projects that don't like to make releases and where it is no problem to use git master. Also looking at the recent commits: most of them seem to be changes to the database, not the library, which is confirmed by this comment:
|
I don't think that including all the files is a suitable solution imho, why not just bump to the latest working commit for now and see when there's a new release of the library. |
If copying from git, consider adding a simple data validator though which checks version since it's in the XML files. Then you can easily see when compat version changes. |
Can we not specify the zip file as a simple archive in the manifest and unzip it to a specific location?
…On May 6, 2020 8:09:35 AM PDT, "Hubert Figuière" ***@***.***> wrote:
> @eszlari we don't want to buld git master though.
No, unless upstream does it.
The lack of recent release of lensfun and the fact that Darktable uses
0.3.95 (which, I read, was not the best idea) is already suboptimal.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#57 (comment)
|
Which zip? The output of And Now to end the bike shedding, I want the shed colour to be fire engine red. |
BTW I could just merge the PR right now. I just wanted to make sure this was not done the wrong way. |
I'm sorry you feel this is bikeshedding, I feel like it is a legitimate discussion.
…On May 6, 2020 11:28:29 AM PDT, "Hubert Figuière" ***@***.***> wrote:
Which zip?
The output of `lensfun-update-data` is a bunch of files, that the
update script here will put into a tarball so it is easier to manage
with the build process of flatpak. Also the tarball is in the repo. I
could avoid checking the db files in, but this is the only reliable way
I found to see if there are actual changes to the database since a
tarball would be different with different modification time of any of
its content. There is not point in doing a new build if the data didn't
change.
And `lensfun-update-data` vs what's in git I'll remind that the former
is the *sanctionned* way to update the data for a distribution without
updating the library. Which is why I picked that route.
_Now to end the bike shedding, I want the shed colour to be fire engine
red._
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#57 (comment)
|
I do think we should wait until we come up with a proper solution instead of just wanting to fix the issue for users. See https://github.com/flathub/flathub/wiki/App-Maintenance#required-files |
Can we specify |
Yes, that's perfectly doable and flathub-external-checker can update it automatically as well |
I'm trying to provide the best to have an update database in the flatpak so that:
I do not see other alternative even in the suggestion in this thread. |
This is already what is being done. But the proiblem is that the tar.bz2 file was generated by the update script I mention because there is no such thing available otherwise. |
Except that this file is not available for download. |
Yes it is: https://wilson.bronger.org/lensfun-db/version_2.tar.bz2 Gnome dictionary does this:
Could we do similar? |
Perhaps something like this
|
Did you look at the .json in this PR?
You mean copy 60 files by hand, install a tarball? |
So the day the tarball change, the build fail and there is no way to do it again. |
Yes so we update the sha256 and build again. |
That's the exact reason why we have flathub-external-data-checker. If the url of an application that we can't re-distribute directly, the bot updates the URL and their checksums each hour automatically and send/merge the pull requests as well. |
But this is not the case of something that can't be redistributed. This is something that can be checked, redistributed, etc. I'll ask the question. What is wrong with the PR? So far I only got told there are alternative for which none of the parameters I listed are fullfilled. This solution even fits the parameters list on the app maintenance wiki page since this is handling a specific problem for a specific solution. I really wish it had been easier, but I haven't found a better way. |
In such case, you can just generate those files in a separate repository, create a tarball and use it from there if it can be redistributed. |
It's an over engineered solution to a problem that doesn't (yet) exist. The manifests on Flathub should strive to be maintainable. What if tomorrow, you are hit by a bus? I think everybody should be able to understand a manifest as easy as possible and submit PRs. Just use a git commit and add a comment to the manifest like:
|
They'd be people in deeper trouble than a flathub repository. Also there is a Anyway it seems that is consensus that you don't like it. Feel free to reopen reuse if you feel there is anything usable. |
This also update the database.
Closes #56