search

scala / bug

Scala 2 bug reports only. Please, no questions — proper bug reports only.
https://scala-lang.org
232 stars 21 forks source link

Repositories with stable/nightly builds for popular Linux distributions #4516

Closed scabug closed 13 years ago

scabug commented 13 years ago

= problem = The packages in most Linux distributions are already outdated at the date of release of those distributions.

Problem is that these Linux distributions think "Newer == less stable" which is not really true at this stage of development.

People who try Scala often end up with these versions (as experienced in Scala's IRC channel).

Additionally it is annoying for nightly testers having to download the newest version (remember to check if new one is available -> look at time stamp -> download -> extract -> rename/fix symlinks -> ...) as tarballs.

= analysis = Getting distributions to ship with a recent/recommended version will be

The only real solution would be to provide an APT/RPM repo, which supplies stable/nightly builds, so that people can just add that repo to their package sources.

There are services which help with that. OpenSuse BuildService, Ubuntu PPA, ...

= enhancement recommendation = Please provide repositories for stable/nightly builds for some of the common Linux distributions. This is comparable to what happens with Maven at the moment.

scabug commented 13 years ago

Imported From: https://issues.scala-lang.org/browse/SI-4516?orig=1 Reporter: @soc

scabug commented 13 years ago

@cunei said: There are several formats that are in used by popular Linux distributions, and each of those require some know-how in order to be prepared correctly. In addition, some Linux distributions also have a specific approval process, that needs to be followed in order for each package to be included as part of those distributions. That requires a great deal of work, and that is the reason why the packaging for individual Linux platform is managed by external contributors, as specified at http://www.scala-lang.org/node/292. As core team, our resources are better spent working on the compiler and the core infrastructure; our contributors are already doing a better job than we would be able to do ourselves.