-
Notifications
You must be signed in to change notification settings - Fork 15
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
Figure out package names of dependencies for various distributions #21
Comments
We have the vimiv package for Fedora but that uses the old code base. Is vimiv-qt ready for inclusion (mature enough for distribution to users)? If yes, would you prefer that I replace vimiv with this new code base, or should I package vimiv-qt as a new package? Since the binary remains vimiv, we can't carry both---they'll conflict. If I add |
Since the versions of vimiv-qt is currently 0.2.0, this cannot be considered an upgrade to vimiv whose latest version is 0.9.0 (0.9.0 > 0.2.0 in semver). So at least in Fedora, we'll have to package vimiv-qt as a new package and obsolete vimiv for the upgrade path to work correctly. |
This actually concerns the names of the required software dependencies to run vimiv, e.g. |
Ah, I'll be able to help with the dep names once I've been able to package the qt port up correctly. If the idea is to only have one repository, the qt development should ideally be done in a The simplest way would probably be to just use this now and leave it as |
I would certainly keep the two repositories as both have their value in some way, but the Qt version should become the "default" at some point. Hopefully with the 0.10 minor release here. You are probably right that keeping it as |
I think simply adding a banner on the old website saying "This is deprecated/archived, please use vimiv-qt instead" should be OK. To discourage its use further, you can archive the github repo, and if necessary remove the documentation from there too? |
Closing in favour of #686 |
The install part of the documentation includes the required package names of the dependencies for different distributions. This should be done for:
The text was updated successfully, but these errors were encountered: