View Single Post
Old 09-10-2022, 02:26 PM   #2
kiwidude
Calibre Plugins Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,726
Karma: 2197770
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
It would mean extra steps in my workflow at least - so I am against those .

Usually we have fairly simple scripts to build the zip files for the latest code - trying to parse version numbers from other files and include that in the zip file name in an automated fashion gets more complicated.

It also means the devs would have more of a mess in our working folders to have to keep cleaning up - rather than a single Goodreads.zip I would over time end up with one for every version I build I have to keep deleting or again add to the build complexity.

Then when you upload to a forum post you must remember to remove the previous zip - not something you have to do if it has the same name.

Basically it would add friction which adds up - at least when you have 27 plugins to maintain as I think my current active count is. Of course if this was my day job it would be a different story - but then I would have a dedicated build server and automation constructing plugin zips after commits, a fileshare to store historic versions etc. And we wouldn't be manually uploading zip files into forum threads
kiwidude is offline