Thread: [Discussion] Update plugins from GitHub release page
View Single Post
Old 11-22-2020, 06:04 PM   #5
BetterRed
null operator
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 16,878
Karma: 19721268
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by theducks View Post
The only reason I can see for changing the current method would be to allow a Version repository (not the Linux type) similar to what Calibre has for its releases.
That way, the PI's would not need to be kept One Size fits most (levels of Calibre)
That could done without any changes to the current scheme of things by providing a link in a plugin's first post to a Github Releases page a'la Sigil ==>> Sigil Releases @ GitHub

BR
Last edited by BetterRed; 11-22-2020 at 06:06 PM.
BetterRed is offline   Reply With Quote