Making one ebuild per one extension seems to me as complicated way. This extensions have been made as git only, so time by time update takes a lot of work 'cause there is no version update. I decided to make one ebuild for some unofficial extensions and manage them by use flags. First I have to say, that I am still learning to make ebuilds, so maybe it won't be perfect (same like my single-extensions -ebuilds) Second notice is about discusion if this way (one ebuild for more extensions) is right. I'd like to hear some opinions about ebuild coding and if this is right way to manage unofficial extensions. Reproducible: Always
Created attachment 276943 [details] gnome-shell-extensions-unofficial-9999.ebuild
Created attachment 276973 [details] gnome-shell-extensions-unofficial-9999.ebuild Updated ebuild for changes in mediasplayers extension
Created attachment 277069 [details] gnome-shell-extensions-unofficial-9999.ebuild Updated ebuild for changes in mediasplayers extension
Created attachment 277225 [details] Updated ebuild for changes in pidgin extension
Is need to remove the gnome-shell-extensions before?