-
Notifications
You must be signed in to change notification settings - Fork 464
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
Release v90 with latest changes on master to support GNOME 46 #2177
Comments
I would like to read it too, if someone knows, please. |
Hey! So basically when you install a software from source, you'll first download the Git repository (I suggest you to watch videos about how Git works, it will be the absolute and most important thing you'll need to learn and master on Linux). If you pull changes from upstream (the server) to your local repo (your machine), you'll just have to re-execute the command to build the software. You will have immediately the latest changes without waiting for a release. But, the obvious downside is if some dev pushes something bad, not much tested, it has the potential to break something. Second, I don't think pre-releases are that useful. It still needs packaging, effort etc... for not much help. You still can build the latest with the git repo, consider this a "pre-release". Even the actual extension isn't a stable release, as it will always contain bugs, break easily when a new GNOME is out, etc... |
Thanks for your responses. @kernelb00t I'm aware of how Git works and Linux. 😆 My question was more related to how GNOME extensions releases are working. How updates are pushed to extensions.gnome.org and how users got the update. Is it automatic? How do users download the update? I hope my questions are now clearer. 😄 |
This is one of the reasons why I would not bother installing directly from Git: it very likely requires maintenance, and returning to the official, non-Git version, might be a hassle. |
@theoludwig you will not be automatically updated. When a new version comes out, you will have to uninstall the source-built copy you had cloned from GitHub and then download from extensions.gnome.org or Extension Manager or whatever you use. |
@theoludwig Sorry, I don't even know why I thought you were a newbie with git. This issue seems resolved. If your question is answered, please close 😉 (and a little thank you message will always be appreciated, we love to know when our answers to people's questions are clear and understandable!) |
It still shows up in |
Hello! 👋
Thank you for making and maintaing this awesome GNOME extension. It's probably the most important extension, I'm using for my GNOME Desktop workflow, and to improve my UX (honestly I don't understand, how it is not integrated in GNOME by default, if anyone has a discussion related to it, I would be curious to read it, if it has already been discussed 👀).
I've just upgraded my Arch Linux to use GNOME 46, and found out, that this extension is not working. So I tried to follow the instructions on the README to install it from source: https://github.com/micheleg/dash-to-dock#installation-from-source, and it seems to work quite well.
It seems like there are still issues related to GNOME 46: #2160, but I think, it's still already worth to release a new version, as broken versus, already working, is already an improvement worth a release IMHO.
Is it possible to do pre-releases? Maybe that would be the solution, to release "not 100% ready".
I'm not familiar with the development of GNOME extensions, it's the first time, I installed one from source, If you publish a new update, will I automatically be updated to the newest version?
The text was updated successfully, but these errors were encountered: