Answer the question
In order to leave comments, you need to log in
Are there systems for storing releases?
Hello.
There are many version control systems for storing program sources. As you know, no one in their right mind stores files obtained as a result of a build in the repository.
I asked myself this question: are there systems for storing releases, already assembled and ready-to-use programs? For example, a user enters this system through a web interface, selects the required project, selects the release version and can download the compiled program, read the changelog, leave a comment, etc.
Google didn't ban me, but found nothing. Probably, I do not guess with the wording of the request.
Thanks for the help.
Answer the question
In order to leave comments, you need to log in
As you know, no one in their right mind stores files obtained as a result of a build in the repository.
GitHub has a release system , binaries can be attached separately from source codes.
Also take a look at SourceForge .
Version control systems can save the entire project. But usually only the originals are saved. It is not clear what prevents you from rolling back to the desired version and building the release
> The issue is to ensure that users always have the ability to download the right release
I think this is a more important issue than the issue identified in the main question.
Why do users need an old release? Why was a new one released if the old one is more in demand?
I often see that different versions on the site are separated by subdomains or subfolders. mysite/v1/file.msi, mysite/v2/file.msi.
This is about users. And if we talk about developers, then there is no point in storing binaries, they can always be rebuilt from source.
What is wrong with the good old packages and their repositories (I mean those that are deb/rpm)? And the same launchpad ?
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question