Re: New repo and some fixes for Gophernicus
On 28 Jan 2018, at 19:25, David Woodfall <dave@dawoodfall.net> wrote:
>
> I'm just thinking about the slackware package maintainer:
> slackbuilds.org will *only* accept a definite version number for
> source tarballs.
Ok, I didn't know that - but does slackbuilds *really* download the specifically versioned file form the original download server every time someone uses slackbuilds? That's pretty dumb - like in this case gophernicus.org doesn't even exist anymoar because it's been confiscated as being part of a huge drug sales ring :D :D :D. The way Debian does it is that the maintainer downloads the sources once, adds a version if it's not there and then uploads the tar file to Debian's servers so it doesn't matter if the original server goes down or not.
But ok, you do have a point, and I think the BSD ports are doing the same thing. Is there a way to upload versioned .tar.gz files to Github? I cannot self-host anything anymore because anything I own will get confiscated eventually so cloud is the only safe place now (but that's just my fault for being the drug lord that I am :D).
Anyway - my primary reason for giving up versioninig is that a "version" doesn't really mean anything since I code whenever I feel like coding. Like before today the release version of Gophernicus was 2.5 - were today's fixes enough for 2.6? Should they have been released as 2.5.1? Should I wait a few more days and a few more fixes before releasing 2.6? Maybe 2.9? When is it time to do 3.0?
Computers were created to help people, not make my life overly complicated :D
I need to think about this and come up with a fix.
- Kim
Reply to: